carlcrott

Code changes should only be pushed to github if all tests are passing.


Below is a common work-flow for a team working with a central repo. 
Variations are possible, but if unsure, please go by this:

1. Git pull (or, if this is your first time ever getting the code, do git clone git@github.com:our_repo/our_repo.git to get a local copy of the repo)
2. Run tests
3. If tests fail, stop here and investigate. Do not continue to develop until all tests are passing.
4. git checkout -b my_work (create and switch to a local branch where you'll do your work)

carlcrott

Carl Crott
Oakland CA
carlcrott@gmail.com
415.304.3670

                        recruiters: please no unsolicited phone calls, email is preferred.

Bio:

carlcrott

Carl Crott
Oakland CA
carlcrott@gmail.com
415.304.3670

                        recruiters: please no unsolicited phone calls, email is preferred.

Bio:

Capable and driven multi-systems engineer with a core focus on UI to DB development and automated infrastructure. Both a technical developer and conversational in research concepts. Experience in scaling, application testing/hardening, linux sysadmin, web scraping, biochem / bioinformatics and design and prototyping of scientific hardware.

chrislerum

Code changes should only be pushed to github if all tests are green.


Below is a common work-flow for a team working with a central repo. several variations are possible, but if unsure, please go by this:

   1. if you are working from a Pivotal Tracker story, click "start" on that story
   2. git pull (or, if this is your first time ever getting the code, do git clone git@github.com:our_repo/our_repo.git to get a local copy of the repo)
   3. rake db:migrate
   4. rake db:test:prepare
   5. spec spec