Skip to content

Commit 2a13d4a

Browse files
Add note about bypass permissions allowing branch renames (#61390)
1 parent 829e11a commit 2a13d4a

3 files changed

Lines changed: 4 additions & 7 deletions

File tree

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -194,7 +194,7 @@ Across all organizations owned by your enterprise, you can allow members with ad
194194

195195
## Enforcing a policy for renaming protected branches
196196

197-
By default, repository administrators can rename branches that are targeted by enterprise-level rules, provided the new branch name is still targeted by those rules. You can restrict this ability to enterprise owners only.
197+
By default, repository administrators can rename branches that are targeted by enterprise-level rules, provided the new branch name is still targeted by those same rules, or the administrator has permission to bypass the rule in question. You can restrict this ability to enterprise owners only.
198198

199199
{% data reusables.enterprise-accounts.access-enterprise %}
200200
{% data reusables.enterprise-accounts.policies-tab %}

content/organizations/managing-organization-settings/allowing-repository-admins-to-rename-branches-with-organization-rulesets.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,12 @@ category:
99
- Configure organization features
1010
---
1111

12-
Organization owners control whether repository administrators can rename branches that are targeted by one or more branch rulesets. For existing organizations, this setting is off by default. For newly created organizations, this setting is on by default.
12+
Organization owners control whether repository administrators can rename branches that are targeted by one or more branch rulesets. For existing organizations, this setting is disabled by default. For newly created organizations, this setting is enabled by default.
1313

14-
When this setting is enabled, repository administrators can rename these branches, provided the new branch name is still targeted by all the same organization rulesets as the current branch name. This ensures that rulesets cannot be circumvented through branch renaming.
14+
When this setting is enabled, repository administrators can rename these branches, provided the new branch name is still targeted by all the same organization rulesets as the current branch name, or the repository administrator has permission to bypass any which are no longer targeted. This ensures that rulesets cannot be circumvented through branch renaming.
1515

1616
Organization administrators can rename branches targeted by organization rulesets without restriction.
1717

18-
> [!NOTE]
19-
> Even with this setting enabled, changing the default branch of a repository still requires an organization administrator when organization rulesets are in play.
20-
2118
{% data reusables.profile.access_org %}
2219
{% data reusables.profile.org_settings %}
2320
{% data reusables.organizations.member-privileges %}

content/repositories/configuring-branches-and-merges-in-your-repository/managing-branches-in-your-repository/renaming-a-branch.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Some branches can only be renamed by a repository administrator: the repository'
3434

3535
When organization-level or enterprise-level rulesets target branches in a repository, renaming those branches typically requires an organization or enterprise administrator.
3636

37-
However, organization and enterprise owners can allow repository administrators to rename branches covered by these rulesets, provided the new branch name is still subject to all the same rules as the current name. Changing the default branch still requires an organization or enterprise administrator when rulesets are in play.
37+
However, organization and enterprise owners can allow repository administrators to rename branches covered by these rulesets, provided the new branch name is still subject to all the same rules as the current name, or the repository administrator has permission to bypass those rules. Changing the default branch works similarly.
3838

3939
For more information, see [AUTOTITLE](/organizations/managing-organization-settings/allowing-repository-admins-to-rename-branches-with-organization-rulesets) and [AUTOTITLE](/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise#enforcing-a-policy-for-renaming-protected-branches).
4040

0 commit comments

Comments
 (0)