You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-governance.md
To learn more, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
19
24
25
+
As you onboard your enterprise, rulesets are how you apply consistent protections across many repositories at once, rather than configuring each repository individually.
26
+
27
+
If you have used **branch protection rules** on individual repositories, rulesets serve a similar goal at enterprise scale. Unlike a branch protection rule, which applies to a single repository, a ruleset can target many organizations, repositories, and branches at the same time, and you can set it to an evaluate status to preview its impact before you enforce it.
28
+
20
29
## Importing rulesets
21
30
22
31
To import a prebuilt ruleset created by {% data variables.product.company_short %}, see [`github/ruleset-recipes`](https://github.com/github/ruleset-recipes).
23
32
24
-
{% data reusables.repositories.import-a-ruleset-conceptual %} For more information, see [AUTOTITLE](/organizations/managing-organization-settings/managing-rulesets-for-repositories-in-your-organization#using-ruleset-history).
25
-
26
33
## How will I define where my ruleset applies?
27
34
28
35
Rulesets allow you to flexibly target the organizations, repositories, and branches where you want rules to apply.
@@ -62,9 +69,7 @@ The following are eligible for bypass access:
62
69
* {% data variables.copilot.copilot_cloud_agent %}. For more information about {% data variables.copilot.copilot_cloud_agent %}, see [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent#limitations-in-copilot-cloud-agents-compatibility-with-other-features).
63
70
{%- endif %}
64
71
65
-
1. To grant bypass permissions for the ruleset, in the "Bypass list" section, click **Add bypass**.
66
-
67
-
1. In the "Add bypass" modal dialog that appears, search for the role, team, or app you would like to grant bypass permissions, then select the role, team, or app from the "Suggestions" section and click Add Selected.
72
+
1. In the "Bypass list" section, click **Add bypass**, then search for and select the role, team, or app you want to grant bypass permissions, and click **Add Selected**.
68
73
69
74
{% data reusables.repositories.rulesets-branch-tag-bypass-optional-step %}
70
75
@@ -125,8 +130,7 @@ You can grant certain roles, teams, or apps bypass permissions as well as the ab
125
130
* {% data variables.copilot.copilot_cloud_agent %}. For more information about {% data variables.copilot.copilot_cloud_agent %}, see [AUTOTITLE](/copilot/concepts/agents/cloud-agent/about-cloud-agent#limitations-in-copilot-cloud-agents-compatibility-with-other-features).
126
131
{%- endif %}
127
132
128
-
1. To grant bypass permissions for the ruleset, in the "Bypass list" section, click **Add bypass**.
129
-
1. In the "Add bypass" modal dialog that appears, search for the role, team, or app you would like to grant bypass permissions, then select the role, team, or app from the "Suggestions" section and click Add Selected.
133
+
1. In the "Bypass list" section, click **Add bypass**, then search for and select the role, team, or app you want to grant bypass permissions, and click **Add Selected**.
130
134
131
135
### Choosing which organizations to target in your enterprise
0 commit comments