-
Notifications
You must be signed in to change notification settings - Fork 5
/
CODEOWNERS
Validating CODEOWNERS rules...
89 lines (69 loc) · 3.57 KB
/
CODEOWNERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
# PURPOSE OF THIS FILE:
# epispot's code is licensed under the GNU v3.0 General Public License,
# meaning you can use any code on the repository and package for your own projects
# provided,
# (1) you give credit to the authors (as described within this file)
# (2) you also use the GNU v3.0 General Public License for your project
# This file provides the authoring information for (1)
# WHAT THIS MEANS FOR CONTRIBUTIONS:
# Every time a CODEOWNER's code is modified in a new PR,
# GitHub will automatically ping them for review.
# Epispot will rarely merge PRs without author approval,
# which means that in order for a PR to be merged into the `master` branch,
# it will need to receive approving reviews from all authors whose code has been modified.
# In the event that a CODEOWNER is unreachable or does not review the PR within a suitable amount of time,
# the PR will be merged regardless.
# However, it may be rejected if it fails in beta trials.
# CODEOWNER GUIDELINES:
# To become a CODEOWNER, you must:
# (1) Directly contribute to a file in this repository
# (2) License your code to epispot under the condition that it will be kept with a GNU v3.0 General Public License
# (3) Submit a PR describing your changes
# (a) If your PR modifies someone else's code,
# you must receive an approving review from them;
# however you will take over as CODEOWNER of the code
# you modified once approved
# (4) Have your PR approved and merged into the latest release of epispot
# (5) Wait until your feature passes beta trials and is released into the main package
# If you believe that you have followed these steps but are not properly attributed to your code within this file,
# please contact an existing CODEOWNER or a repository maintainer to have your GitHub username registered in this
# document.
# Additionally, if you would like your username *removed* from this document,
# follow the same steps listed above.
# IMPORTANT NOTES:
# Please note that due to current GitHub processes, if you do not have write access to the repository,
# many of the features of CODEOWNERS will not work for your account. However, you will be manually pinged after
# your code is touched.
# Please see the official GitHub document on CODEOWNERS at:
# https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
* @quantum9innovation
*.py @quantum9innovation
*.sh @quantum9innovation
*.md @quantum9innovation
*.txt @quantum9innovation
*.csv @quantum9innovation
*.png @quantum9innovation
# formerly @Quantalabs ↓
*.toml @quantum9innovation
*.gitignore @quantum9innovation
# *.yml @Quantalabs
# *.cfg @Quantalabs
# *.coveragerc @Quantalabs
scripts/ @quantum9innovation
# formerly @Quantalabs ↓
requirements/ @quantum9innovation
requirements-* @quantum9innovation
# formerly @Quantalabs ↓
/scripts/ @quantum9innovation
# /.github/ @Quantalabs
# /.github/workflows/* @Quantalabs
/.github/ISSUE_TEMPLATE/ @quantum9innovation
/epispot/ @quantum9innovation
test_* @quantum9innovation
*-nightly @quantum9innovation
*-dev @quantum9innovation
LICENSE @quantum9innovation
# formerly @quantum9Innovation @Quantalabs ↓
SECURITY.md @quantum9innovation
# formerly @Quantalabs ↓
setup.py @quantum9innovation