-
Notifications
You must be signed in to change notification settings - Fork 32
Branch Update Workflow
Erik A. Roberts edited this page Dec 14, 2017
·
9 revisions
Monthly (last Friday of each month), the branches should be merged in a particular manner:
- cd to dynasim repo:
cd "path/to/repo" - Unit test debug and proceed if no errors
- Update master from debug
git checkout master- Merge debug into master with
git merge debug --no-commit, so that one can still edit the commit - Confirm master is production-ready
- fix conflicts
- check qsub* permissions are
a+x - add hard copy of submodules, like MDD
- remove any dev files, like
demos/devDemos git commit
- Update dev from debug
git checkout devgit merge debug- fix conflicts, check qsub* permissions are
a+x, and commit
- Update debug from updated dev
git checkout debuggit merge dev- fix conflicts, check qsub* permissions are
a+x, and commit
- Push all changes:
git push --all
At this point, master is now the same as the old debug branch, but with hard-copied submodules. Debug and dev should be identical. For the next month, debug branch will be tested and debugged, while dev is for new features. The average developer should be using debug, and adding features to dev.