Skip to content

Commit c5bca24

Browse files
authored
Update contribution doc to use CLA (#9)
Update contribution doc to use CLA
1 parent f8e2e36 commit c5bca24

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

CONTRIBUTING.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
#Contributing to the Optimizely JavaScript SDK
22

3-
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.
3+
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.
44

55
## Development process
66

7-
1. Create a branch off of `master`: `git checkout -b YOUR_NAME/branch_name`.
7+
1. Create a branch off of `devel`: `git checkout -b YOUR_NAME/branch_name`.
88
2. Commit your changes. Make sure to add tests!
99
3. Run `npm run lint` to ensure there are no lint errors.
1010
4. Run `webpack` to generate the built and minified file for those not installing via `npm`
1111
5. `git push` your changes to GitHub.
12-
6. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `master`.
13-
7. Open a pull request from `YOUR_NAME/branch_name` to `master`.
12+
6. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `devel`.
13+
7. Open a pull request from `YOUR_NAME/branch_name` to `devel`.
1414
8. A repository maintainer will review your pull request and, if all goes well, merge it!
1515

1616
##Pull request acceptance criteria

0 commit comments

Comments
 (0)