Skip to content

Commit a3e2ed9

Browse files
author
Jake Harding
committedFeb 25, 2013
Update CONTRIBUTING.md.
1 parent f1f96a7 commit a3e2ed9

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed
 

‎CONTRIBUTING.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -12,16 +12,15 @@ Writing Code
1212

1313
* Use the project's coding style, not your own. If the code you write looks drastically different than the preexisting code, you're doing it wrong.
1414
* Include tests that fail without your code, and pass with it.
15-
* If you add a new feature or break backwards compatibility, update the project's documentation accordingly.
1615
* Commits should have meaningful messages. If you end up with a bunch of commits with garbage messages, squash your commits before submitting a pull request.
1716

1817
Pull Requests
1918
-------------
2019

2120
1. Push your feature branch to your remote repo on GitHub. `$ git push origin name-of-feature`
22-
2. [Create a pull request][create-pull-request] against the integration-\* branch if present, otherwise master.
23-
3. Write a meaningful title and description.
24-
4. Submit the pull request!
21+
2. [Create a pull request][create-pull-request] against master.
22+
3. Write a meaningful title and description. If you've added a new feature or break backwards compatibility, let us know so we can updated the docs accordingly.
23+
5. Submit the pull request!
2524

2625
[how-to-fork]: https://help.github.com/articles/fork-a-repo
2726
[create-pull-request]: https://help.github.com/articles/creating-a-pull-request

0 commit comments

Comments
 (0)
Please sign in to comment.