Teams plans support org level rulesets (#56029)

Co-authored-by: Copilot <[email protected]>
Co-authored-by: Anne-Marie <[email protected]>

Author: 3 people

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

@@ -2,7 +2,9 @@
 title: Creating rulesets for repositories in your organization
 intro: 'You can create a ruleset to target multiple repositories in your organization.'
 versions:
-  feature: repo-rules-enterprise
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.13'
 permissions: 'Organization owners can create rulesets at the organization level.'
 topics:
   - Organizations
@@ -11,7 +13,7 @@ shortTitle: Create rulesets
 
 ## Introduction
 
-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.
+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.
 
 {% ifversion push-rulesets %}
 
@@ -39,10 +41,13 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
 {% data reusables.repositories.rulesets-fnmatch %}
 {% ifversion repo-rules-enterprise %}
 
+{% ifversion not fpt %}
+
 ## Using regular expressions for commit metadata
 
 {% data reusables.repositories.rulesets-commit-regex %}
 
+{% endif %}
 {% endif %}
 
 ## Using ruleset enforcement statuses
@@ -57,10 +62,13 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
 {% data reusables.repositories.create-ruleset-step %}
 {% data reusables.repositories.rulesets-general-step %}
 
+{% ifversion not fpt %}
+
 ### Granting bypass permissions for your branch or tag ruleset
 
 {% data reusables.repositories.rulesets-bypass-step %}
 {% data reusables.repositories.rulesets-branch-tag-bypass-optional-step %}
+{% endif %}
 
 ### Choosing which repositories to target in your organization
 
@@ -74,9 +82,12 @@ To import one of the prebuilt rulesets by {% data variables.product.prodname_dot
 
 {% data reusables.repositories.rulesets-protections-step %}
 
+{% ifversion not fpt %}
+
 ### Adding metadata restrictions
 
 {% data reusables.repositories.rulesets-metadata-step %}
+{% endif %}
 
 ### Finalizing your branch or tag ruleset and next steps
 

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

@@ -16,9 +16,7 @@ shortTitle: Custom properties
 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.
 An organization can have up to 100 property definitions. An allowed value list can have up to 200 items.
 
-{% ifversion ghec or ghes %}
 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).
-{% endif %}
 
 {% ifversion ghec %}
 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

@@ -2,7 +2,9 @@
 title: Managing rulesets for repositories in your organization
 intro: 'You can edit, monitor, and delete existing rulesets to alter how people can interact with repositories in your organization.'
 versions:
-  feature: repo-rules-enterprise
+  fpt: '*'
+  ghec: '*'
+  ghes: '>= 3.13'
 permissions: 'Organization owners and users with the "Manage organization ref update rules and rulesets" permission can manage rulesets at the organization level.'
 topics:
   - Organizations
@@ -11,7 +13,7 @@ shortTitle: Manage rulesets
 
 ## About managing rulesets for an organization
 
-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.
+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.
 
 {% ifversion push-rule-delegated-bypass %}
 
@@ -64,6 +66,7 @@ You can import a ruleset from another repository or organization using the expor
 {% data reusables.repositories.import-a-ruleset %}
 
 {% endif %}
+{% ifversion not fpt %}
 
 ## Viewing insights for rulesets
 
@@ -83,3 +86,4 @@ You can view insights for rulesets to see how rulesets are affecting the reposit
 {% data reusables.repositories.managing-delegated-bypass %}
 
 {% endif %}
+{% endif %}

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

@@ -14,7 +14,7 @@ shortTitle: About rulesets
 
 ## About rulesets
 
-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 %}.
+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.
 
 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).
 

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

@@ -26,8 +26,7 @@ When you create a ruleset, you can allow certain users to bypass the rules in th
 
 For more information on rulesets, see [AUTOTITLE](/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets).
 
-{% ifversion repo-rules-enterprise %}
-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 %}
+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).
 
 {% ifversion repo-rules-management %}