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: docs/developmentguide.rst
+6-25Lines changed: 6 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,46 +61,27 @@ Try to auto-fix pep8 styling issues by
61
61
62
62
Pull Request (PR) Procedure
63
63
---------------------------
64
-
* fork our project and create a new branch.
64
+
* fork our project and create a new branch
65
65
* clone it and check this branch out
66
66
* apply your desired changes / extensions
67
-
* commit and push it to remote. Please follow these format rules_.
68
-
We suggest to use commitizen_.
69
-
* open a pull request (PR) - check results of Travis CI.
70
-
There are possibly Code issues you can correct.
67
+
* commit and push it to remote. Please follow these [commit guidelines](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines). We suggest to use [commitizen](https://github.com/commitizen/cz-cli/blob/master/README.md).
68
+
* open a pull request (PR).
69
+
* check if the Travis CI build check fails. If so, review your code (feel free to ask for help).
70
+
* squash your commits as far as it makes sense
71
+
* rebase your branch
71
72
72
73
**We care then about the rest** - no need to worry about things like
73
74
building current realease and versioning.
74
75
75
76
**You can stop here.**
76
77
77
-
The below sections are just for our reference.
78
78
TIA for your PR and thus for your support of this project. As we have
79
79
further SDKs in other languages, it might take a bit of time to check
80
80
if we can role out that PR as we want to keep all our SDKs aligned.
0 commit comments