Published: 12 Feb 2018 › Updated: 12 Feb 2018
How to best use of Git -GitFlow
A successful Git branching model:
Master Branch:
- origin/master to be the main branch where the source code of HEAD always reflects a production-ready state.
- All of the changes should be merged back into master somehow and then tagged with a release number.
Develop Branch:
- origin/develop to be the main branch where the source code of HEAD always reflects a state with the latest delivered development changes for the next release.
Gitflow Supporting Branches:
- Feature
- Release
- Hotfix
Feature branches:
- Must branch off from: develop
- Must merge back into: develop
- Branch naming convention: anything I prefer “JobNumber-JobTitle/#JIRATicketNumber”?
Release branches:
- Must branch off from: develop
- Must merge back into: develop + Master
- Branch naming convention: anything I prefer “Release-*(ReleaseNumber)”.
HotFixes Branches:
- Must branch off from: master
- Must merge back into: develop + Master
- Branch naming convention: I prefer “hotfix-*(#JIRATicketNumber)”
Summary:
Here is the Google slide link that I have created if anyone interested.
https://docs.google.com/presentation/d/18t1VhjoWoLx73GopDpEjvJ0kBPwMzZXrL2-kzJyjj_0/edit?usp=sharing:
Please let me know if you have any questions.
Leave How to best use of Git -GitFlow to:
Read more #git posts
Best Posts From dheerajp
We have not curated any of dheerajp's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From dheerajp
- How to best use of Git -GitFlow
- Self assigned SSL certificate for Solr
- Execution terminated in fault state - Neo-Gui
- The world is not any more it use to be in crypto
- Disconectttttttt
- Written a Neo smart contract worth it?
- Fed up with coinbase commission fee?
- Wassa wassa wassaaaaaaa Bitconneeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeet
- Adventures in replying to spam
- Altcoins are not on sale!!!