Skip to content

Commit 3eb3f98

Browse files
patrick-knightCopilotam-stead
authored
Teams plans support org level rulesets (#56029)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Anne-Marie <102995847+am-stead@users.noreply.github.com>
1 parent 021e923 commit 3eb3f98

File tree

5 files changed

+21
-9
lines changed

5 files changed

+21
-9
lines changed

content/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@
22
title: Creating rulesets for repositories in your organization
33
intro: 'You can create a ruleset to target multiple repositories in your organization.'
44
versions:
5-
feature: repo-rules-enterprise
5+
fpt: '*'
6+
ghec: '*'
7+
ghes: '>= 3.13'
68
permissions: 'Organization owners can create rulesets at the organization level.'
79
topics:
810
- Organizations
@@ -11,7 +13,7 @@ shortTitle: Create rulesets
1113

1214
## Introduction
1315

14-
You can create rulesets in your organization to control how users can interact with repositories in your organization. You can control things like who can push commits to a certain branch and how the commits must be formatted, or who can delete or rename a tag. You can also prevent people from renaming repositories.
16+
For customers on {% data variables.product.prodname_team %} or {% data variables.product.prodname_enterprise %} plans you can create rulesets in your organization to control how users can interact with repositories in your organization. You can control things like who can push commits to a certain branch and how the commits must be formatted, or who can delete or rename a tag. You can also prevent people from renaming repositories.
1517

1618
{% ifversion push-rulesets %}
1719

@@ -39,10 +41,13 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
3941
{% data reusables.repositories.rulesets-fnmatch %}
4042
{% ifversion repo-rules-enterprise %}
4143

44+
{% ifversion not fpt %}
45+
4246
## Using regular expressions for commit metadata
4347

4448
{% data reusables.repositories.rulesets-commit-regex %}
4549

50+
{% endif %}
4651
{% endif %}
4752

4853
## Using ruleset enforcement statuses
@@ -57,10 +62,13 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
5762
{% data reusables.repositories.create-ruleset-step %}
5863
{% data reusables.repositories.rulesets-general-step %}
5964

65+
{% ifversion not fpt %}
66+
6067
### Granting bypass permissions for your branch or tag ruleset
6168

6269
{% data reusables.repositories.rulesets-bypass-step %}
6370
{% data reusables.repositories.rulesets-branch-tag-bypass-optional-step %}
71+
{% endif %}
6472

6573
### Choosing which repositories to target in your organization
6674

@@ -74,9 +82,12 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
7482

7583
{% data reusables.repositories.rulesets-protections-step %}
7684

85+
{% ifversion not fpt %}
86+
7787
### Adding metadata restrictions
7888

7989
{% data reusables.repositories.rulesets-metadata-step %}
90+
{% endif %}
8091

8192
### Finalizing your branch or tag ruleset and next steps
8293

content/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,9 +16,7 @@ shortTitle: Custom properties
1616
Custom properties allow you to decorate your repositories with information such as compliance frameworks, data sensitivity, or project details. Custom properties visibility follows the visibility of the repository. Custom properties on public repositories can be viewed by anyone, while custom properties on internal or private repositories can be viewed by accounts with read permissions to the repository.
1717
An organization can have up to 100 property definitions. An allowed value list can have up to 200 items.
1818

19-
{% ifversion ghec or ghes %}
2019
You can use repository properties to determine which repositories to target with a ruleset. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization#targeting-repositories-by-properties-in-your-organization).
21-
{% endif %}
2220

2321
{% ifversion ghec %}
2422
You can define custom properties at the enterprise level to create a consistent experience across organizations. See [AUTOTITLE](/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise).

content/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,9 @@
22
title: Managing rulesets for repositories in your organization
33
intro: 'You can edit, monitor, and delete existing rulesets to alter how people can interact with repositories in your organization.'
44
versions:
5-
feature: repo-rules-enterprise
5+
fpt: '*'
6+
ghec: '*'
7+
ghes: '>= 3.13'
68
permissions: 'Organization owners and users with the "Manage organization ref update rules and rulesets" permission can manage rulesets at the organization level.'
79
topics:
810
- Organizations
@@ -11,7 +13,7 @@ shortTitle: Manage rulesets
1113

1214
## About managing rulesets for an organization
1315

14-
After creating a ruleset at the organization level, you can make changes to the ruleset to alter how people can interact with the targeted repositories. For example, you can add rules to better protect the branches or tags in those repositories, or you can switch your ruleset from "Evaluate" mode to "Active" after testing its effects on the contributor experience for your repositories. Organizational rulesets that apply to branches of a repository will no longer allow the repository administrator to rename branches of the targeted repository or change the default branch to another branch. Repository administrators may create and delete branches so long as they have the appropriate permissions.
16+
After creating a ruleset at the organization level, you can make changes to the ruleset to alter how people can interact with the targeted repositories. For example, you can add rules to better protect the branches or tags in those repositories{% ifversion not fpt %}, or you can switch your ruleset from "Evaluate" mode to "Active" after testing its effects on the contributor experience for your repositories{% endif %}. Organizational rulesets that apply to branches of a repository will no longer allow the repository administrator to rename branches of the targeted repository or change the default branch to another branch. Repository administrators may create and delete branches so long as they have the appropriate permissions.
1517

1618
{% ifversion push-rule-delegated-bypass %}
1719

@@ -64,6 +66,7 @@ You can import a ruleset from another repository or organization using the expor
6466
{% data reusables.repositories.import-a-ruleset %}
6567

6668
{% endif %}
69+
{% ifversion not fpt %}
6770

6871
## Viewing insights for rulesets
6972

@@ -83,3 +86,4 @@ You can view insights for rulesets to see how rulesets are affecting the reposit
8386
{% data reusables.repositories.managing-delegated-bypass %}
8487

8588
{% endif %}
89+
{% endif %}

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ shortTitle: About rulesets
1414

1515
## About rulesets
1616

17-
A ruleset is a named list of rules that applies to a repository{% ifversion repo-rules-enterprise %}, or to multiple repositories in an organization{% endif %}. You can have up to 75 rulesets per repository{% ifversion repo-rules-enterprise %}, and 75 organization-wide rulesets{% endif %}.
17+
A ruleset is a named list of rules that applies to a repository or to multiple repositories in an organization for customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans. You can have up to 75 rulesets per repository, and 75 organization-wide rulesets.
1818

1919
When you create a ruleset, you can allow certain users to bypass the rules in the ruleset. This can be users with a certain role, such as repository administrator, or it can be specific teams or {% data variables.product.prodname_github_apps %}. For more information about granting bypass permissions, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository#granting-bypass-permissions-for-your-ruleset).
2020

content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,7 @@ When you create a ruleset, you can allow certain users to bypass the rules in th
2626

2727
For more information on rulesets, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
2828

29-
{% ifversion repo-rules-enterprise %}
30-
You can also create rulesets for all repositories in an organization. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization).{% endif %}
29+
For customers on {% data variables.product.prodname_team %} and {% data variables.product.prodname_enterprise %} plans you can also create rulesets for repositories in an organization. For more information, see [AUTOTITLE](/organizations/managing-organization-settings/creating-rulesets-for-repositories-in-your-organization).
3130

3231
{% ifversion repo-rules-management %}
3332

0 commit comments

Comments
 (0)