Merge pull request #26637 from github/repo-sync

Repo sync

content/actions/deployment/protecting-deployments/creating-custom-deployment-protection-rules.md

@@ -78,6 +78,10 @@ Once a workflow reaches a job that references an environment that has the custom
 
 1. Optionally, review the deployment on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[AUTOTITLE](/actions/managing-workflow-runs/reviewing-deployments)."
 
+{% ifversion fpt or ghec %}
+
 ## Publishing custom deployment protection rules in the {% data variables.product.prodname_marketplace %}
 
 You can publish your {% data variables.product.prodname_github_app %} to the {% data variables.product.prodname_marketplace %} to allow developers to discover suitable protection rules and install it across their {% data variables.product.company_short %} repositories. Or you can browse existing custom deployment protection rules to suit your needs. For more information, see "[AUTOTITLE](/apps/publishing-apps-to-github-marketplace/github-marketplace-overview/about-github-marketplace)" and "[AUTOTITLE](/apps/publishing-apps-to-github-marketplace/listing-an-app-on-github-marketplace)."
+
+{% endif %}

content/admin/monitoring-activity-in-your-enterprise/exploring-user-activity/viewing-push-logs.md

@@ -29,7 +29,7 @@ Push log entries show:
 
 {% ifversion repository-activity-view %}
 {% data reusables.repositories.activity-view %}
-For more information, see "[Using the activity view to see changes to your repository](/enterprise-server@latest/repositories/viewing-activity-and-data-for-your-repository/viewing-repository-activity#using-the-activity-view-to-see-changes-to-a-repository)."
+For more information, see "[AUTOTITLE](/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository)."
 {% endif %}
 
 ## Viewing a repository's push logs

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md

@@ -192,7 +192,7 @@ If you added manual build steps for compiled languages and {% data variables.pro
 
 {% data reusables.code-scanning.beta-swift-support %}
 
-Code scanning of Swift code uses macOS runners by default. Since {% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, we recommend that you build only the code that you want to analyze. For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+Code scanning of Swift code uses macOS runners by default. {% ifversion fpt or ghec %}Since {% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, we recommend that you build only the code that you want to analyze. For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
 
 `xcodebuild` and `swift build` are both supported for Swift builds. We recommend only targeting one architecture during the build. For example, `ARCH=arm64` for `xcodebuild`, or `--arch arm64` for `swift build`.
 

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/customizing-code-scanning.md

@@ -158,7 +158,7 @@ This workflow scans:
 {% ifversion codeql-swift-beta %}
 {% note %}
 
-**Note**: Code scanning of Swift code uses macOS runners by default. {% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, so you should consider only scanning the build step. For more information about configuring code scanning for Swift, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages#considerations-for-building-swift)." For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
+**Note**: Code scanning of Swift code uses macOS runners by default. {% ifversion fpt or ghec %}{% data variables.product.company_short %}-hosted macOS runners are more expensive than Linux and Windows runners, so you should consider only scanning the build step. For more information about configuring code scanning for Swift, see "[AUTOTITLE](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages#considerations-for-building-swift)." For more information about pricing for {% data variables.product.company_short %}-hosted runners, see "[AUTOTITLE](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."{% endif %}
 
 {% endnote %}
 

content/rest/orgs/personal-access-tokens.md

@@ -3,8 +3,7 @@ title: Personal access tokens
 shortTitle: Personal access tokens
 intro: 'Use the REST API to manage {% data variables.product.pat_v2 %}s.'
 versions:
-  fpt: '*'
-  ghec: '*'
+  feature: pat-v2
 topics:
   - API
 autogenerated: rest

content/rest/orgs/rules.md

@@ -4,7 +4,7 @@ shortTitle: Rules
 intro: 'Use the rulesets API to manage rulesets for repositories. Organization rulesets control how people can interact with selected branches and tags in repositories in an organization.'
 versions:
   fpt: '*'
-  ghec: '*'
+  feature: repo-rules-enterprise
 topics:
   - API
 autogenerated: rest

content/rest/repos/rules.md

@@ -4,7 +4,7 @@ shortTitle: Rules
 intro: 'Use the rulesets API to manage rulesets for repositories. Rulesets control how people can interact with selected branches and tags in a repository.'
 versions:
   fpt: '*'
-  ghec: '*'
+  feature: repo-rules-enterprise
 topics:
   - API
 autogenerated: rest