Add GHES 3.18 support for enterprise repository custom properties docs (#62381)

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: sbauer <54006+sbauer@users.noreply.github.com>
Co-authored-by: Shane Bauer <sbauer@github.com>

Author: Copilot

content/admin/concepts/enterprise-fundamentals/enterprise-accounts.md

@@ -60,7 +60,7 @@ Teams can be synced with IdP groups, allowing you to manage any privileges that
 
 Repositories host files such as your company's source code or internal documentation. They are where developers typically do their work, and they contain their own features and administration options that need to live closer to the code, such as {% data variables.product.prodname_actions %} workflows.
 
-Repositories are owned by organizations and are not directly accessible under the enterprise account.{% ifversion custom-properties-enterprise %} However, your enterprise can define custom properties to apply the same governance model to all repositories with shared characteristics. For example, if you do not want anyone to delete repositories that contain production code, this is something you can govern from the enterprise level.{% endif %}
+Repositories are owned by organizations and are not directly accessible under the enterprise account.{% ifversion custom-properties-enterprise %} However, your enterprise can define custom properties to apply the same governance model to all repositories with shared characteristics.{% endif %} {% ifversion repo-policy-rules %} For example, if you do not want anyone to delete repositories that contain production code, this is something you can govern from the enterprise level.{% endif %}
 
 {% ifversion ghec %}
 

content/admin/managing-accounts-and-repositories/managing-repositories-in-your-enterprise/managing-custom-properties-for-repositories-in-your-enterprise.md

@@ -13,7 +13,7 @@ category:
 
 Custom properties allow you to decorate your repositories with information such as compliance frameworks, data sensitivity, or project details. Custom properties are private and can only be viewed by people with read permissions to the repository. An enterprise can have up to 100 property definitions. An allowed value list can have up to 200 items.
 
-Defining custom properties at the enterprise level allows you to create consistent values that users can apply to repositories. With custom properties in place, you can apply consistent governance across repositories in your enterprise by creating a ruleset or repository policy targeting repositories with certain properties.
+Defining custom properties at the enterprise level allows you to create consistent values that users can apply to repositories. With custom properties in place, you can apply consistent governance across repositories in your enterprise by creating a ruleset{% ifversion repo-policy-rules %} or repository policy{% endif %} targeting repositories with certain properties.
 
 ## Allowed characters
 

data/features/custom-properties-enterprise.yml

@@ -1,3 +1,4 @@
 # Repository custom properties defined at the enterprise level
 versions:
   ghec: '*'
+  ghes: '>= 3.18'