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
2. create a branch with an explicit name (like ``my-new-feature`` or ``issue-XX``)
28
-
3. do your work in it
29
-
4. rebase it on the master branch from the official repository (cleanup your history by performing an interactive rebase)
30
-
5. add you change to the changelog
31
-
6. submit your pull-request
30
+
2. Ensure an issue is opened for your feature or bug
31
+
3. create a branch with an explicit name (like ``my-new-feature`` or ``issue-XX``)
32
+
4. do your work in it
33
+
5. Commit your changes. Ensure the commit message includes the issue. Also, if contributing from a corporation, be sure to add a comment with the Copyright information
34
+
6. rebase it on the master branch from the official repository (cleanup your history by performing an interactive rebase)
35
+
7. add you change to the changelog
36
+
8. submit your pull-request
37
+
9. 2 Maintainers should review the code for bugfix and features. 1 maintainer for minor changes (such as docs)
38
+
10. After review, a maintainer a will merge the PR. Maintainers should not merge their own PRs
32
39
33
40
There are some rules to follow:
34
41
@@ -51,7 +58,7 @@ An Invoke ``tasks.py`` is provided to simplify the common tasks:
51
58
Available tasks:
52
59
53
60
all Run tests, reports and packaging
54
-
assets Fetch web assets
61
+
assets Fetch web assets -- Swagger. Requires NPM (see below)
55
62
clean Cleanup all build artifacts
56
63
cover Run tests suite with coverage
57
64
demo Run the demo
@@ -86,3 +93,28 @@ and the documentation is properly generating.
0 commit comments