-
Notifications
You must be signed in to change notification settings - Fork 221
Development Process
Xiaohan Zhang edited this page Aug 28, 2017
·
8 revisions
- Pull latest develop
- Create a branch off of develop, usually named after the ticket (ex: "
1791fix1
", "1684ER
", etc). - Work and commit on branch.
- Write tests, and then run all tests with
yarn test
. - Push branch to remote.
- Create a pull request from your branch into develop.
- Assign a developer to review (one of @hellochar, @CalvinFernandez, or @themadcreator).
- If you receive a [-1], back to step 3 to address concerns.
- Pull latest develop.
- Create a feature branch off of develop.
- Follow steps 2 through 8 above, but cutting off and merging into your feature branch instead of **develop. Tag any pull requests with the [Side Branch] tag.
Especially useful in going back in history, if builds are stable at every commit, we can safely go to that commit to check for functionality at that point in time.