diff options
| author | Anthony Lavado <anthonylavado@users.noreply.github.com> | 2018-12-12 23:28:42 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-12-12 23:28:42 -0500 |
| commit | c9f324af9f3cd28150f413f0ea8b6fda9d2dff10 (patch) | |
| tree | 9d84eb83a1970143227e62a649b48b12e3fd0125 | |
| parent | af520f0e3aff9cd8b617dbb16374d6e3d5d8d467 (diff) | |
| parent | 7b171fd33aea11e2297236b3c51fb5082956ac49 (diff) | |
Merge pull request #124 from LeoVerto/patch-1
Update CONTRIBUTING.md to new branching guidelines
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index b5fd212c9..1b1bc3b72 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -25,7 +25,7 @@ We adhere to a fairly standard fork-and-PR model of development: 2. Make your changes on a local feature branch of your copy of the repository. -3. Submit a pull request from your feature branch back to the upstream master branch. +3. Submit a pull request from your feature branch back to the upstream develop branch. If your PR includes *only* documentation or text file changes you should submit it against master. All PRs require review before merging. Once that is done, if the PR is not tagged with the WIP label, it should be immediately merged by the reviewer assuming that they have write access. If you do not have write access, please feel free to leave reviews as well and suggest changes as they will be taken into account as well. |