What is the GitLab Flow
- A simplified branching strategy
- All features and fixes first go to master
- Allows for ‘production’ or ‘stable’ branches
- Bug fixes/hot fix patches are cherry-picked from master
Feature branches
- Create a feature/bugfix branch to do all work
- Use merge requests to merge to master
Production branch
- One, long-running production release branch as opposed to individual stable branches
- Consider creating a tag for each version that gets deployed
Production branch
Release branch
- Useful if you release software to customers
- When preparing a new release, create stable branch from master
- Consider creating a tag for each version
- Cherry-pick critical bug fixes to stable branch for patch release
- Never commit bug fixes directly to stable branch
Release branch
More details
For more information, read through the GitLab Flow documentation.
Help and feedback
If there's something you don't like about this feature
To propose functionality that GitLab does not yet offer
To further help GitLab in shaping new features
If you didn't find what you were looking for
If you want help with something very specific to your use case, and can use some community support
POST ON GITLAB FORUM
If you have problems setting up or using this feature (depending on your GitLab subscription)
REQUEST SUPPORT
To view all GitLab tiers and features or to upgrade
If you want to try all features available in GitLab.com
If you want to try all features available in GitLab self-managed
If you spot an error or a need for improvement and would like to fix it yourself in a merge request
EDIT THIS PAGE
If you would like to suggest an improvement to this doc