Find below typical Git branching strategy followed in agile teams:
- Feature branch – developers may create this branchy for mostly every story during sprint.
- Develop branch – after feature is developed, code will be merged to develop branch.
- Release branch – Create this branch for every release, fix the defects raised during QA and release all the way to PROD.
- Master branch – current prod release code. Once after every release, code needs to merged from release branch to master branch to keep the code in sync.
- Hot fix branch - For any urgent bug fixes, after the fix is done, code needs to be merged to develop branch and master branch.
ReplyDeleteit is a useful article when i compared to others.thanks for this wonderful article and im really happy to read this.
DevOps certification in Chennai
DevOps Training in Chennai
DevOps course in Chennai
Data science course in chennai
AWS training in chennai
AWS certification in chennai
Nice blog.Thanks for sharing.
ReplyDeleteDevOps course in Pune
9BF771D877
ReplyDeletehacker arıyorum
hacker kirala
tütün dünyası
-
-
Great summary! Branch discipline is often underestimated, especially in agile sprints where speed matters. Having a defined release branch ensures stability before merging to master. It would be interesting to see how Git strategies evolve with GitOps practices in cloud-native environments.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteoperating on, and I have been on the look out for such information disc certification
ReplyDelete