Highest extra value wins if there's a conflict (should never interfere with other rules)
Use sourcetree code#
User and group access overrides anything else (ALLOW vs DENY is unspecified, since existing code only uses ALLOW here)Īnything can override non-branch specific access Rules for branch permission priority (condensed version of what gets enforced) For example: PROJECT-* to limit access to all branches with names like PROJECT-1234. Use branch permissionsīranch permissions help enforce specific workflows and prevent errors like a new workspace member deleting the main branch.Ĭlosely control which users or groups can write or merge to any branch.Ĭreate permissions for a specific branch type, or pattern. See the sections below for more specifics on using branch permissions, including branch types and branch patterns, and setting merge checks. Select Branch restrictions on the left navigation sidebar. Select Project Settings on the left navigation sidebar. Select the project in which you want to add branch restrictions.
Select Projects on the top navigation bar to access the projects within the workspace. Access and add project branch restrictions
Note: Project branch restrictions are no different than repository branch restrictions when it comes to enforcement and administration.Īs an admin, you may want to set branch restrictions within a project to create a consistent set of branch permissions and merge checks across all the repositories within the project, meaning all the branch restrictions set within a project are enforced on every repository within that project so you don’t have to set branch restrictions per repository. Project branch restrictions are a way for an admin to set branch permissions and merge settings across all the repositories within a project.
0 kommentar(er)
