Skip to content

Commit f6b1a76

Browse files
Updating contribution doc to use CLA (#26)
1 parent 37c8bc8 commit f6b1a76

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
#Contributing to the Optimizely Python SDK
2-
We welcome contributions and feedback! Please read the [README](README.md) to set up your development environment, then read the guidelines below for information on submitting your code.
2+
We welcome contributions and feedback! All contributors must sign our [Contributor License Agreement (CLA)](https://docs.google.com/a/optimizely.com/forms/d/e/1FAIpQLSf9cbouWptIpMgukAKZZOIAhafvjFCV8hS00XJLWQnWDFtwtA/viewform) to be eligible to contribute. Please read the [README](README.md) to set up your development environment, then read the guidelines below for information on submitting your code.
33

44
##Development process
55

6-
1. Create a branch off of `master`: `git checkout -b YOUR_NAME/branch_name`.
6+
1. Create a branch off of `devel`: `git checkout -b YOUR_NAME/branch_name`.
77
2. Commit your changes. Make sure to add tests!
88
3. Lint your changes before submitting with `pep8 YOUR_CHANGED_FILES.py`.
99
4. `git push` your changes to GitHub.
10-
5. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `master`.
11-
6. Open a pull request from `YOUR_NAME/branch_name` to `master`.
10+
5. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `devel`.
11+
6. Open a pull request from `YOUR_NAME/branch_name` to `devel`.
1212
7. A repository maintainer will review your pull request and, if all goes well, merge it!
1313

1414
##Pull request acceptance criteria

0 commit comments

Comments
 (0)