/
Git Branching Strategy

Git Branching Strategy

 

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

Related content

Component Design Framework
Component Design Framework
Read with this
Git Branching and Pull Request Workflow
Git Branching and Pull Request Workflow
More like this
Forms Design + Submission - Forminators team landscape
Forms Design + Submission - Forminators team landscape
Read with this
Openshift and DevOps
Openshift and DevOps
More like this
Openshift Deployment Prerequisites
Openshift Deployment Prerequisites
Read with this
Forking Repository
Forking Repository
More like this