@@ -9,15 +9,16 @@ read the guidelines below for information on submitting your code.
9
9
Development process
10
10
-------------------
11
11
12
- 1. Create a branch off of ``master ``:
13
- ``git checkout -b YOUR_NAME/branch_name ``.
14
- 2. Commit your changes. Make sure to add tests!
15
- 3. Lint your changes before submitting: ``pep8 YOUR_CHANGED_FILES.py ``.
16
- 4. ``git push `` your changes to GitHub.
17
- 5. Make sure that all unit tests are passing and that there are no merge
12
+ 1. Fork the repository and create your branch from master.
13
+ 2. Please follow the `commit message guidelines `_ for each commit message.
14
+ 3. Make sure to add tests!
15
+ 4. Run ``pep8 `` to ensure there are no lint errors.
16
+ 5. ``git push `` your changes to GitHub.
17
+ 6. Open a PR from your fork into the master branch of the original repo.
18
+ 7. Make sure that all unit tests are passing and that there are no merge
18
19
conflicts between your branch and ``master ``.
19
- 6 . Open a pull request from ``YOUR_NAME/branch_name `` to ``master ``.
20
- 7 . A repository maintainer will review your pull request and, if all
20
+ 8 . Open a pull request from ``YOUR_NAME/branch_name `` to ``master ``.
21
+ 9 . A repository maintainer will review your pull request and, if all
21
22
goes well, squash and merge it!
22
23
23
24
Pull request acceptance criteria
@@ -76,5 +77,6 @@ If you have questions, please contact developers@optimizely.com.
76
77
77
78
.. _Contributor License Agreement (CLA) : https://docs.google.com/a/optimizely.com/forms/d/e/1FAIpQLSf9cbouWptIpMgukAKZZOIAhafvjFCV8hS00XJLWQnWDFtwtA/viewform
78
79
.. _README : README.rst
80
+ .. _commit message guidelines : https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines
79
81
.. _deviations : https://github.com/optimizely/python-sdk/blob/master/tox.ini
80
- .. _Apache License v2.0 : http://www.apache.org/licenses/LICENSE-2.0
82
+ .. _Apache License v2.0 : http://www.apache.org/licenses/LICENSE-2.0
0 commit comments