Skip to content

Instantly share code, notes, and snippets.

@erinnachen
Last active December 18, 2018 16:48
Show Gist options
  • Save erinnachen/1f802734671d9db5c452 to your computer and use it in GitHub Desktop.
Save erinnachen/1f802734671d9db5c452 to your computer and use it in GitHub Desktop.
My Git Workflow

Project workflow:

  1. Load/Reload waffle.
  2. 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.
  3. git checkout master
  4. git pull origin master
  5. run rspec
  6. Checkout a new branch and tag it with #issue_number
  7. Write the feature test associated with your waffle card.
  8. Run rspec, and make sure that there are no errors that blow up the stack (missing ends, forgetting capitalization, etc.)
  9. commit your feature test
  10. push this up to github, and create a [WIP] pull request.
  11. start implementing the features
  12. when you commit, remember to push up to remote, and wait for hound to respond
  13. 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.
  14. Correct the hound issues you have, go to step 10.
  15. When your feature test passes, commit and push up to GitHub. Wait for those hound requests to come back in.
  16. Deal with hound. Push up to Github. Repeat until hound is dealt with.
  17. Search the project for binding.pry and save_and_open_pages leftover. Take those remnants out of the code.
  18. Run rails s and see if everything looks and behaves like you want it to. Fix those and commit. Deal with hound.
  19. If there are really obvious sad paths for your feature test, you should write that test and return to Step 10.
  20. Rebase and squash the commits that you do not want record for posterity.
  21. Check if your branch comes from the latest master, and if not pull master into your branch.
  22. Run rspec one more time
  23. Remove [WIP] from pull request. If you're not paired, tag others and ping slack for a code review.
  24. After code is merged to master, remember to push to heroku with git push heroku master and heroku run rake db:migrate
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment