Branches

Branches are versions of a project’s working tree. When you create a new project, GitLab creates a default branch (which cannot be deleted) for your repository. Default branch settings can be configured at the project, subgroup, group, or instance level.

As your project grows, your team creates more branches, preferably by following branch naming patterns. Each branch represents a set of changes, which allows development work to be done in parallel. Development work in one branch does not affect another branch.

Branches are the foundation of development in a project:

  1. To get started, create a branch and add commits to it.
  2. When the work is ready for review, create a merge request to propose merging the changes in your branch. To streamline this process, you should follow branch naming patterns.
  3. Preview changes in a branch with a review app.
  4. After the contents of your branch are merged, delete the merged branch.

Create branch

Prerequisites:

  • You must have at least the Developer role for the project.

To create a new branch from the GitLab UI:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Branches.
  3. On the top right, select New branch.
  4. Enter a Branch name.
  5. In Create from, select the base of your branch: an existing branch, an existing tag, or a commit SHA.
  6. Select Create branch.

In a blank project

A blank project does not contain a branch, but you can add one.

Prerequisites:

  • You must have at least the Developer role for the project.
  • If you don’t have the Maintainer or Owner role, the default branch protection must be set to Partially protected or Not protected for you to push a commit to the default branch.

To add a default branch to an empty project:

  1. On the left sidebar, select Search or go to and find your project.
  2. Scroll to The repository for this project is empty and select the type of file you want to add.
  3. In the Web IDE, make any desired changes to this file, then select Create commit.
  4. Enter a commit message, and select Commit.

GitLab creates a default branch and adds your file to it.

From an issue

Prerequisites:

  • You must have at least the Developer role for the project.

When viewing an issue, you can create an associated branch directly from that page. Branches created this way use the default pattern for branch names from issues, including variables.

Prerequisites:

  • You must have at least the Developer role for the project.

To create a branch from an issue:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Plan > Issues and find your issue.
  3. Below the issue description, find the Create merge request dropdown list, and select to display the dropdown list.
  4. Select Create branch. A default Branch name is provided, based on the default pattern for this project. If desired, enter a different Branch name.
  5. Select Create branch to create the branch based on your project’s default branch.

Manage and protect branches

GitLab provides multiple methods to protect individual branches. These methods ensure your branches receive oversight and quality checks from their creation to their deletion:

  • The default branch in your project receives extra protection.
  • Configure protected branches to restrict who can commit to a branch, merge other branches into it, or merge the branch itself into another branch.
  • Configure approval rules to set review requirements, including security-related approvals, before a branch can merge.
  • Integrate with third-party status checks to ensure your branch contents meet your standards of quality.

You can manage your branches:

View all branches

To view and manage your branches in the GitLab user interface:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Branches.

On this page, you can:

  • See all branches, or filter to see only active or stale branches.
  • Create new branches.
  • Compare branches.
  • Delete merged branches.

View branches with configured protections

Version history
On self-managed GitLab, by default this feature is available. To hide the feature, an administrator can disable the feature flag named branch_rules. On GitLab.com, this feature is available.

Branches in your repository can be protected in multiple ways. You can:

  • Limit who can push to the branch.
  • Limit who can merge the branch.
  • Require approval of all changes.
  • Require external tests to pass.

The Branch rules overview page shows all branches with any configured protections, and their protection methods:

Example of a branch with configured protections

Prerequisites:

  • You must have at least the Maintainer role for the project.

To view the Branch rules overview list:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > Repository.
  3. Expand Branch rules to view all branches with protections.
    • To add protections to a new branch:
      1. Select Add branch rule.
      2. Select Create protected branch.
    • To view more information about protections on an existing branch:
      1. Identify the branch you want more information about.
      2. Select View details to see information about its:

Name your branch

Git enforces branch name rules to help ensure branch names remain compatible with other tools. GitLab adds extra requirements for branch names, and provides benefits for well-structured branch names.

GitLab enforces these additional rules on all branches:

  • No spaces are allowed in branch names.
  • Branch names with 40 hexadecimal characters are prohibited, because they are similar to Git commit hashes.

Common software packages, like Docker, can enforce additional branch naming restrictions.

For the best compatibility with other software packages, use only:

  • Numbers
  • Hyphens (-)
  • Underscores (_)
  • Lowercase letters from the ASCII standard table

You can use forward slashes (/) and emoji in branch names, but compatibility with other software packages cannot be guaranteed.

Branch names with specific formatting offer extra benefits:

Configure default pattern for branch names from issues

By default, GitLab uses the pattern %{id}-%{title} when creating a branch from an issue, but you can change this pattern.

Prerequisites:

  • You must have at least the Maintainer role for the project.

To change the default pattern for branches created from issues:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > Repository.
  3. Expand Branch defaults.
  4. Scroll to Branch name template and enter a value. The field supports these variables:
    • %{id}: The numeric ID of the issue.
    • %{title}: The title of the issue, modified to use only characters acceptable in Git branch names.
  5. Select Save changes.

Prefix branch names with issue numbers

To streamline the creation of merge requests, start your Git branch name with the issue number, followed by a hyphen. For example, to link a branch to issue #123, start the branch name with 123-.

The issue and the branch must be in the same project.

GitLab uses the issue number to import data into the merge request:

  • The issue is marked as related to the merge request. The issue and merge request display links to each other.
  • The branch is connected to the issue.
  • If your project is configured with a default closing pattern, merging the merge request also closes the related issue.
  • Issue milestone and labels are copied to the merge request.

Compare branches

To compare branches in a repository:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Compare revisions.
  3. Select the Source branch to search for your desired branch. Exact matches are shown first. You can refine your search with operators:
    • ^ matches the beginning of the branch name: ^feat matches feat/user-authentication.
    • $ matches the end of the branch name: widget$ matches feat/search-box-widget.
    • * matches using a wildcard: branch*cache* matches fix/branch-search-cache-expiration.
    • You can combine operators: ^chore/*migration$ matches chore/user-data-migration.
  4. Select the Target repository and branch. Exact matches are shown first.
  5. Below Show changes, select the method to compare branches:
    • Only incoming changes from source (default) shows differences from the source branch since the latest common commit on both branches. It doesn’t include unrelated changes made to the target branch after the source branch was created. This method uses the git diff <from>...<to> Git command. To compare branches, this method uses the merge base instead of the actual commit, so changes from cherry-picked commits are shown as new changes.
    • Include changes to target since source was created shows all the differences between the two branches. This method uses the git diff <from> <to> Git command.
  6. Select Compare to show the list of commits, and changed files.
  7. Optional. To reverse the Source and Target, select Swap revisions ().

Delete merged branches

Merged branches can be deleted in bulk if they meet all of these criteria:

  • They are not protected branches.
  • They have been merged into the project’s default branch.

Prerequisites:

  • You must have at least the Developer role for the project.

To do this:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Branches.
  3. On the upper right corner of the page, select More .
  4. Select Delete merged branches.
  5. In the dialog, enter the word delete to confirm, then select Delete merged branches.

Troubleshooting

Multiple branches containing the same commit

At a deeper technical level, Git branches aren’t separate entities, but labels attached to a set of commit SHAs. When GitLab determines whether or not a branch has been merged, it checks the target branch for the existence of those commit SHAs. This behavior can cause unexpected results when two merge requests contain the same commits. In this example, branches B and C both start from the same commit (3) on branch A:

gitGraph commit id:"a" branch "branch A" commit id:"b" commit id:"c" type: HIGHLIGHT branch "branch B" commit id:"d" checkout "branch A" branch "branch C" commit id:"e" checkout main merge "branch B" id:"merges commits b, c, d"

If you merge branch B, branch A also appears as merged (without any action from you) because all commits from branch A now appear in the target branch main. Branch C remains unmerged, because commit 5 wasn’t part of branch A or B.

Merge request A remains merged, even if you attempt to push new commits to its branch. If any changes in merge request A remain unmerged (because they weren’t part of merge request A), open a new merge request for them.

Error: ambiguous HEAD branch exists

In versions of Git earlier than 2.16.0, you could create a branch named HEAD. This branch named HEAD collides with the internal reference (also named HEAD) Git uses to describe the active (checked out) branch. This naming collision can prevent you from updating the default branch of your repository:

Error: Could not set the default branch. Do you have a branch named 'HEAD' in your repository?

To fix this problem:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Code > Branches.
  3. Search for a branch named HEAD.
  4. Make sure the branch has no uncommitted changes.
  5. Select Delete branch, then Yes, delete branch.

Git versions 2.16.0 and later, prevent you from creating a branch with this name.