Carmer/git-workflow.markdown

## git-workflow.markdown

      
    Raw
  

              git-workflow.markdown
            
          
    Project workflow:


Load/Reload waffle.
Choose a card from the backlog in waffle. If we're working separately, it's best to move that card that you've chosen into ready and perhaps assign it to yourself as well.
git checkout master
git pull origin master
run your test suite
Checkout a new branch and tag it with #issue_number
Write the feature test associated with your waffle card.
Run your test suite and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
commit your feature test
push this up to github, and create a [WIP] pull request.
start implementing the features
when you commit, remember to push up to remote, and wait for hound to respond
If there is an issue, ping other people and make question comments with references on your pull request. Wait for aid. Remember to ping on the slack channel as well.
Correct the hound issues you have, go to step 10.
When your feature test passes, commit and push up to GitHub. Wait for those hound requests to come back in.
Deal with hound. Push up to Github. Repeat until hound is dealt with.
Search the project for binding.pry and save_and_open_pages leftover. Take those remnants out of the code.
Run rails s and see if everything looks and behaves like you want it to. Fix those and commit. Deal with hound.
If there are really obvious sad paths for your feature test, you should write that test and return to Step 10.
Rebase and squash the commits that you do not want record for posterity.
Check if your branch comes from the latest master, and if not pull master into your branch.
Run your test suite one more time
Remove [WIP] from pull request. If you're not paired, tag others and ping slack for a code review.
After code is merged to master, remember to push to heroku with git push heroku master and heroku run rake db:migrate