Commit 4fc57b5872feddb3521478659bee6f9b9da838ef

Authored by Kyle Fazzari
1 parent 168afa02

Updated contribution guidelines to specify MRs should be to master.

Showing 1 changed file with 1 additions and 1 deletions   Show diff stats
CONTRIBUTING.md
@@ -63,7 +63,7 @@ If you can, please submit a merge request with the fix or improvements including @@ -63,7 +63,7 @@ If you can, please submit a merge request with the fix or improvements including
63 1. Add your changes to the [CHANGELOG](CHANGELOG) 63 1. Add your changes to the [CHANGELOG](CHANGELOG)
64 1. If you have multiple commits please combine them into one commit by [squashing them](http://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) 64 1. If you have multiple commits please combine them into one commit by [squashing them](http://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits)
65 1. Push the commit to your fork 65 1. Push the commit to your fork
66 -1. Submit a merge request (MR) 66 +1. Submit a merge request (MR) to the master branch
67 1. The MR title should describes the change you want to make 67 1. The MR title should describes the change you want to make
68 1. The MR description should give a motive for your change and the method you used to achieve it 68 1. The MR description should give a motive for your change and the method you used to achieve it
69 1. If the MR changes the UI it should include before and after screenshots 69 1. If the MR changes the UI it should include before and after screenshots