You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+27-11
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,28 @@
1
1
# Contributing and pull request process
2
2
3
-
To contribute, please send an email to [email protected], or ping us on gitter with what you plan to do (unless uncontroversial and/or small), so that we can agree on the best way to implement it.
4
-
5
-
We appreciate small commits that do one thing, but also that, when possible, each commit doesn't break the master branch. Please use your best judgement for the size of the commit according to these guidelines. If a commit breaks master, we at least require to push together all commits until master is fixed.
6
-
7
-
We also appreciate a tidy history, so after you write all your code, consider tidying up the commits to reflect what you did at the end, which is usually a simplified version of the process that you followed to reach the final state. Moreover, each commit should not have PEP 8 or pyflakes warnings (see below for how to make sure you don't introduce any).
8
-
9
-
If your change involves more than one commit, please create a PR for each of them, unless for very small and obvious commits (read: fixing typos, comments, a few obvious lines), or unless some commit breaks master.
10
-
11
-
During the review, please address all comments by creating one or more 'fixup' commits on top of the branch (no forced push). At the end, either you or one of the owners can squash appropriately the fixups.
ping us on [Telegram](https://t.me/contestms) with what you plan to do (unless
5
+
uncontroversial and/or small), so that we can agree on the best way to implement
6
+
it.
7
+
8
+
We appreciate small commits that do one thing, but also that, when possible,
9
+
each commit doesn't break the master branch. Please use your best judgement for
10
+
the size of the commit according to these guidelines. If a commit breaks master,
11
+
we at least require to push together all commits until master is fixed.
12
+
13
+
We also appreciate a tidy history, so after you write all your code, consider
14
+
tidying up the commits to reflect what you did at the end, which is usually a
15
+
simplified version of the process that you followed to reach the final state.
16
+
Moreover, each commit should not have PEP 8 or pyflakes warnings (see below for
17
+
how to make sure you don't introduce any).
18
+
19
+
If your change involves more than one commit, please create a PR for each of
20
+
them, unless for very small and obvious commits (read: fixing typos, comments, a
21
+
few obvious lines), or unless some commit breaks master.
22
+
23
+
During the review, please address all comments by creating one or more 'fixup'
24
+
commits on top of the branch (no forced push). At the end, either you or one of
25
+
the owners can squash appropriately the fixups.
12
26
13
27
# Code style
14
28
@@ -17,9 +31,11 @@ For Python code, we generally follow [PEP 8](https://www.python.org/dev/peps/pep
17
31
We get around Python flexible type system in several ways:
18
32
* we try to avoid "magic" (e.g., generating or changing classes on the fly);
19
33
* we are fairly verbose with naming, trying to help the reader with following the types;
20
-
* we follow our type annotation system for method and function docstrings (planning to switch to [PEP 484](https://www.python.org/dev/peps/pep-0484/)); see later for the format.
34
+
* we follow our type annotation system for method and function docstrings
35
+
(planning to switch to [PEP 484](https://www.python.org/dev/peps/pep-0484/));
36
+
see later for the format.
21
37
22
-
We support Python 3 only, requiring at least version 3.8.
38
+
We support Python 3 only, requiring at least version 3.9.
0 commit comments