Skip to main content
  1. Learn center
  2. Software Development
  3. Guides
  4. Git tutorial
  5. Git collaboration
  6. Branching workflows
  7. Release branch
GuidesSoftware DevelopmentBacklog
Git

Project and code management together.

Release branch

When you roll out a new release, you create a release branch. A release branch helps you ensure the new features are running correctly.

By convention, start with the prefix release- when naming the release branch.

Typically you would create the release branch off the develop branch when it’s close to being production-ready.

Team members should address only bug fixes and release-related issues on this branch. This allows other team members to continue pushing new features to the develop branch without interrupting the release workflow.

When ready to release, merge the release branch with the main branch and tag a release number to the newly created merge commit.

You should also merge the release branch with the develop branch so that both the main and develop branches receive the latest changes/bug fixes from the release branch.

Subscribe to our newsletter

Learn with Nulab to bring your best ideas to life