Contributing Code to Formhub
Vernon Cole edited this page May 20, 2014
·
3 revisions
-
any new code must have new tests for all new functionality
- it is more efficient to use Test Driven Development
- write tests before, or as, writing new functionality
- info on TDD
- get remote code from the server
- clone the master branch for the latest stable version
git clone git@github.com:SEL-Columbia/formhub.git
- if you have already cloned, pull the latest code
git pull origin master- pull from the
masterbranch
- clone the master branch for the latest stable version
- create a new branch for your changes, we will call it 'new-version'
git checkout -b new-version
- check if something on your computer does not match remote
git status
- show changes to code
git diff
- saving changed code as finished
git commit file.py -m "[message for file]"
- putting changed code on the server
git push origin new-version
- viewing local branches
git branch
- viewing all branches
git branch -a
- checking out another branch
git checkout -t new-version
- get remote code for 'new-version'
git pull origin new-version
- your branch must pass all tests before it will be merged
python manage.py test
- go to github and create a pull request