Here is an essay version of my class notes from Class 1 of CS183: Startup. Errors and omissions are my own. Credit for good stuff is Peter’s entirely.
CS183: Startup—Notes Essay—The Challenge of the Future
Purpose and Preamble
Here is an essay version of my class notes from Class 1 of CS183: Startup. Errors and omissions are my own. Credit for good stuff is Peter’s entirely.
CS183: Startup—Notes Essay—The Challenge of the Future
Purpose and Preamble
| 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. Pull | |
| $ git pull | |
| ... or, if this is your first time ever getting the code, do: | |
| $ git clone [email protected]:our_repo/our_repo.git |
| 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 [email protected]: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 |