-
Notifications
You must be signed in to change notification settings - Fork 3
Git Workflow
TheSuperDuck edited this page Oct 10, 2018
·
4 revisions
The authoritative history of the project, in which every commit should be succinct, atomic, well documented, and error-free
Examples: master, develop, and public feature branches
Your scratch paper while working out a problem
- Create a private feature branch off a public branch other than master
- Regularly commit your work to this private branch
- Once your code is perfect, clean up its history and squash all Work in Progress commits
- Merge the cleaned-up branch back into the public branch
- Merge all new changes to develop
- When the code is production-ready, merge develop into master with the
--no-ffflag - To release a new version, tag the master branch with the version number in the form of "v
major.minor.patch"
A successful Git branching model: https://nvie.com/posts/a-successful-git-branching-model/
Understanding the Git Workflow: https://sandofsky.com/blog/git-workflow.html