GitSwarm 2016.3-2 Documentation

• Protected Branches
  • Configuring protected branches
  • Wildcard protected branches
  • Restrict the creation of protected branches
  • Error messages when pushing to a protected branch
  • Changelog

Protected Branches

Permissions in GitSwarm are fundamentally defined around the idea of having read or write permission to the repository and branches. To prevent people from messing with history or pushing code without review, we've created protected branches.

By default, a protected branch does four simple things:

• it prevents its creation, if not already created, from everybody except users with Master permission
• it prevents pushes from everybody except users with Master permission
• it prevents anyone from force pushing to the branch
• it prevents anyone from deleting the branch

See the Changelog section for changes over time.

Configuring protected branches

To protect a branch, you need to have at least Master permission level. Note that the master branch is protected by default.

1. Navigate to the main page of the project.

2. In the upper right corner, click the settings wheel and select Protected branches.

   

3. From the Branch dropdown menu, select the branch you want to protect and click Protect. In the screenshot below, we chose the develop branch.

   

4. Once done, the protected branch will appear in the "Already protected" list.

   

Since GitSwarm 2016.10, we added another layer of branch protection which provides more granular management of protected branches. You can now choose the option "Developers can merge" so that Developer users can merge a merge request but not directly push. In that case, your branches are protected from direct pushes, yet Developers don't need elevated permissions or wait for someone with a higher permission level to press merge.

You can set this option while creating the protected branch or after its creation.

Wildcard protected branches

Note: This feature was introduced in GitSwarm 2016.10.

You can specify a wildcard protected branch, which will protect all branches matching the wildcard. For example:

Protected branch settings (like "Developers can push") apply to all matching branches.

Two different wildcards can potentially match the same branch. For example, *-stable and production-* would both match a production-stable branch. In that case, if any of these protected branches have a setting like "Allowed to push", then production-stable will also inherit this setting.

If you click on a protected branch's name that is created using a wildcard, you will be presented with a list of all matching branches:

Restrict the creation of protected branches

Creating a protected branch or a list of protected branches using the wildcard feature, not only you are restricting pushes to those branches, but also their creation if not already created.

Error messages when pushing to a protected branch

A user with insufficient permissions will be presented with an error when creating or pushing to a branch that's prohibited, either through GitSwarm's UI:

or using Git from their terminal:

remote: GitSwarm: You are not allowed to push code to protected branches on this project.
To https://gitswarm.example.com/thedude/bowling.git
 ! [remote rejected] staging-stable -> staging-stable (pre-receive hook declined)
error: failed to push some refs to 'https://gitswarm.example.com/thedude/bowling.git'

Changelog

8.10.0

• Allow specifying protected branches using wildcards gitlab-org/gitlab-ce!5081