Shiloh/brotherton-erpnext
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fixed spelling

Browse Source
This commit is contained in:
Valmik 2016-04-20 13:55:48 +05:30
parent 867dfec64b
commit 12bff6ed7c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
.github/CONTRIBUTING.md vendored
View File

@ -47,7 +47,7 @@ If you rebased your commits, you will have to [force push](http://vignette2.wiki
###Good practices: ###Good practices:
* You should rebase your branch with the branch you plan to make a Pull Request to as often as you can. * You should rebase your branch with the branch you plan to make a Pull Request to as often as you can.
* Your commit messages should be Pull Requestecise and explain exactly what the commit does. Same goes for the Pull Request title. * Your commit messages should be precise and explain exactly what the commit does. Same goes for the Pull Request title.
* When making a PR make sure that all your code is committed properly by checking the diffs. * When making a PR make sure that all your code is committed properly by checking the diffs.
* If you're working on different things at the same time, make sure you make separate branches for each. * If you're working on different things at the same time, make sure you make separate branches for each.
* Don't create new DocTypes unless absolutely necessary. If you find that there is a another DocType with a similar functionality, then please try and extend that functionality. * Don't create new DocTypes unless absolutely necessary. If you find that there is a another DocType with a similar functionality, then please try and extend that functionality.
@ -58,4 +58,4 @@ If you rebased your commits, you will have to [force push](http://vignette2.wiki
###Glossary ###Glossary
* remote - A remote is a connection to a Github repo. You should have two remotes, one that points to your repo and one to ours. * remote - A remote is a connection to a Github repo. You should have two remotes, one that points to your repo and one to ours.
* rebase - When you rebase a branch, you pull commits from your remote branch and move your commits on top of it. This allows you to update your branch with the latest changes without losing your changes. * rebase - When you rebase a branch, you pull commits from your remote branch and move your commits on top of it. This allows you to update your branch with the latest changes without losing your changes.