A branch is a version of a project’s working tree. You create a branch for each set of related changes you make. This keeps each set of changes separate from each other, allowing changes to be made in parallel, without affecting each other.
After pushing your changes to a new branch, you can:
- Create a merge request
- Perform inline code review
- Discuss your implementation with your team
- Preview changes submitted to a new branch with Review Apps.
With GitLab Starter, you can also request approval from your managers.
For more information on managing branches using the GitLab UI, see:
You can also manage branches using the command line.
Watch the video GitLab Flow.
- Branches API, for information on operating on repository branches using the GitLab API.
- GitLab Flow documentation.
- Getting started with Git and GitLab.
When you create a new project, GitLab sets
master as the default
branch for your project. You can choose another branch to be your project’s
default under your project’s Settings > Repository.
The default branch is the branch affected by the issue closing pattern, which means that an issue will be closed when a merge request is merged to the default branch.
The default branch is also protected against accidental deletion. Read through the documentation on protected branches to learn more.
To compare branches in a repository:
- Navigate to your project’s repository.
- Select Repository > Compare in the sidebar.
- Select branches to compare using the branch filter search box
- Click Compare to view the changes inline:
Delete merged branches
Introduced in GitLab 8.14.
This feature allows merged branches to be deleted in bulk. Only branches that have been merged and are not protected will be deleted as part of this operation.
It’s particularly useful to clean up old branches that were not deleted automatically when a merge request was merged.
Branch filter search box
This feature allows you to search and select branches quickly. Search results appear in the following order:
- Branches with names that matched search terms exactly.
- Other branches with names that include search terms, sorted alphabetically.
Sometimes when you have hundreds of branches you may want a more flexible matching pattern. In such cases you can use the following:
^featurewill only match branch names that begin with ‘feature’.
feature$will only match branch names that end with ‘feature’.