Skip to content

Commit c3b182a

Browse files
authored
Update CONTRIBUTING.md (#46)
1 parent 770961c commit c3b182a

File tree

1 file changed

+22
-20
lines changed

1 file changed

+22
-20
lines changed

CONTRIBUTING.md

Lines changed: 22 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
# Contributing to the Optimizely PHP SDK
2+
23
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.
34

45
## Development process
56

6-
1. Create a branch off of `devel`: `git checkout -b YOUR_NAME/branch_name`.
7+
1. Create a branch off of `master`: `git checkout -b YOUR_NAME/branch_name`.
78
2. Commit your changes. Make sure to add tests!
89
3. `git push` your changes to GitHub.
9-
4. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `devel`.
10-
5. Open a pull request from `YOUR_NAME/branch_name` to `devel`.
11-
6. A repository maintainer will review your pull request and, if all goes well, merge it!
10+
4. Make sure that all unit tests are passing and that there are no merge conflicts between your branch and `master`.
11+
5. Open a pull request from `YOUR_NAME/branch_name` to `master`.
12+
6. A repository maintainer will review your pull request and, if all goes well, squash and merge it!
1213

1314
## Pull request acceptance criteria
1415

@@ -20,24 +21,25 @@ We welcome contributions and feedback! All contributors must sign our [Contribut
2021
All contributions are under the CLA mentioned above. For this project, Optimizely uses the Apache 2.0 license, and so asks that by contributing your code, you agree to license your contribution under the terms of the [Apache License v2.0](http://www.apache.org/licenses/LICENSE-2.0). Your contributions should also include the following header:
2122

2223
```
23-
/**
24-
* Copyright YEAR, Optimizely, Inc. and contributors
25-
*
26-
* Licensed under the Apache License, Version 2.0 (the "License");
27-
* you may not use this file except in compliance with the License.
28-
* You may obtain a copy of the License at
29-
*
30-
* http://www.apache.org/licenses/LICENSE-2.0
31-
*
32-
* Unless required by applicable law or agreed to in writing, software
33-
* distributed under the License is distributed on an "AS IS" BASIS,
34-
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
35-
* See the License for the specific language governing permissions and
36-
* limitations under the License.
37-
*/
38-
```
24+
/****************************************************************************
25+
* Copyright YEAR, Optimizely, Inc. and contributors *
26+
* *
27+
* Licensed under the Apache License, Version 2.0 (the "License"); *
28+
* you may not use this file except in compliance with the License. *
29+
* You may obtain a copy of the License at *
30+
* *
31+
* http://www.apache.org/licenses/LICENSE-2.0 *
32+
* *
33+
* Unless required by applicable law or agreed to in writing, software *
34+
* distributed under the License is distributed on an "AS IS" BASIS, *
35+
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. *
36+
* See the License for the specific language governing permissions and *
37+
* limitations under the License. *
38+
***************************************************************************/
39+
```
3940

4041
The YEAR above should be the year of the contribution. If work on the file has been done over multiple years, list each year in the section above. Example: Optimizely writes the file and releases it in 2014. No changes are made in 2015. Change made in 2016. YEAR should be “2014, 2016”.
4142

4243
## Contact
44+
4345
If you have questions, please contact [email protected].

0 commit comments

Comments
 (0)