![]() Is ignored in favor of the group level setting. ![]() Group and project levels, the Allowed to force push setting at the project level Specific branch is configured with Allowed to force push settings at both the These settings are inheritedīy all projects in the group and can’t be overridden by project settings. Group owners can create protected branches for a group. To make it available, an administrator can On self-managed GitLab, by default this feature is not available. From the Allowed to merge list, select a role that can merge into this branch.įrom the Allowed to push and merge list, select a role that can push to this branch.From the Branch dropdown list, select the branch you want to protect.On the left sidebar, select Search or go to and find your project.On a protected branch, the group must be added to the project. When granting a group Allowed to merge or Allowed to push and merge permissions.You must have at least the Maintainer role.That matches v1.x must set Allowed to push and merge to No one, like this:Īdministrators can set a default branch protection level in theĬonfigure protected branches for all projects in a group, or just for a project. If you want to ensure that No one is allowed to push to branch v1.x, every pattern To be certain that a rule controls the behavior of a branch,Īll other patterns that match must apply less or equally permissive rules. That also match v1.x or v1.* receive the more permissive Maintainer permission. Even though branches matching v* are set to No one, branches Allowed to push and merge: Of the three settings, Maintainer is the most permissive, and controlsīranch behavior as a result.(which each have stricter permissions), users with the Developer role can merge into the branch. Even though the branch also matched v1.x and v* Allowed to merge: Of the three settings, Maintainer + Developer is most permissive,Īnd controls branch behavior as a result.For example, consider these rules, which includeĪ branch named v1.x is a case-sensitive match for all three branch name patterns: v1.x, v1.*, and v*.Īs the most permissive option determines the behavior, the resulting permissions for branch v1.x are: When a branch matches multiple rules, the most permissive rule determines the ![]() To prevent protected branches being unprotected or deleted. Protected at both the group and project levels, force push settings configuredįor that branch at the project level are ignored.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |