Git Branching Strategy

Owned by Keyvan Torkanpoory
Last updated: Apr 28, 2022 by Anurag Kusumba (Deactivated)
1 min read

 

Git Branching Strategy

feature branch:

  • Feature branch is where developers will start developing their code.

  • Each individual developer will have their own feature branch.

  • To get their changes approved by other developers and reviewers, developers have to raise Pull Requests (PRs).

 
develop branch:

  • In this branch developer will test their code.

  • New developers will always use this branch to create a feature branch from it.

  • Development branch will or should always have reviewed code.

release branch:

  • This branch will have stable / tested code.

  • From this branch we should be able to deploy the code to UAT (user acceptance testing) and demo environments.
                    

hotfix branch:

  • All the critical and major bugs found in production environment, will be fixed in this branch.

  • A similar fix is reflected in development, once the fix is released into the production environment.

main branch:

  • main branch will be used for all deployments into production.

  • Developers or anyone else will be unable to perform any kind of write operations to this branch by default.

Reference: Github Flow https://docs.github.com/en/get-started/quickstart/github-flow