Configuring Protected Branch Rules

Protected Branch Rules Overview

CodeArts Repo makes a code branch more secure by preventing anyone other than the administrator from committing code, preventing anyone from forcibly committing code, or from deleting the branch. You can set this branch to be protected.

Video Tutorial

Constraints

Project manager or project administrator can configure project-level protected branch rules. For details, see Configuring Project-Level Permissions.

Configuring Protected Branch Rules

If you want all repository groups and repositories in this project to use the preceding settings, select Force Inherit.

1. On the CodeArts Repo homepage, access the Scrum_Test project. In the top navigation bar, choose Settings > Policy Settings > Protected Branches and click Create Protected Branch.
2. Set the master branch as a protected branch so that no one can merge code to it except for the committer. See the following figure.

   If a branch contains a single slash (/), the branch cannot be matched using the wildcard * due to the fnmatch syntax rule.

   

   Table 1 Create Protected Branch parameters

   Parameter	Description
   Select target branches to be protected	Enter a complete branch name or a branch name with wildcard characters as required. Only one branch can be added at a time. Batch addition is not supported. The value must start with refs/heads/ and can end with *. Special characters are not allowed in other positions.
   Add permissions	The following permissions can be added: Push. A user with this permission can push code to branches. Merge. A user with this permission can merge, rebase, close, reopen, update patchset, and edit basic attributes (including title, approver/reviewer/merger, work item, and patchset-lock). Create or delete a branch. A user with this permission can add a protected branch or delete it.

   

   • After Allow forced push is enabled, users who have the branch push permission can use the force push command to overwrite the protected branch, but cannot delete the branch.
   • If you have selected Prevent git push-f command in Commit Rules, this function will be invalid.

Helpful Links

When you commit a code file, if an error message indicating you have no permission to commit to the target protected branch (DEV-23-8040) is displayed, the branch you are committing is a protected branch and you need to contact an administrator to grant you the commit permission.