Merge pull request #39453 from github/repo-sync

docs-bot · web-flow · commit 2e938af823b0 · 2025-07-22T11:37:06.000-07:00
Repo sync
diff --git a/content/actions/how-tos/administering-github-actions/index.md b/content/actions/how-tos/administering-github-actions/index.md
@@ -9,7 +9,6 @@ versions:
 children:
   - /viewing-github-actions-metrics
   - /making-retired-namespaces-available-on-ghecom
-  - /managing-custom-actions
 redirect_from:
   - /actions/administering-github-actions
 ---
diff --git a/content/actions/how-tos/creating-and-publishing-actions/creating-a-third-party-cli-action.md b/content/actions/how-tos/creating-and-publishing-actions/creating-a-third-party-cli-action.md
@@ -1,14 +1,14 @@
 ---
-title: Developing a third party CLI action
-shortTitle: CLI setup action
+title: Creating a third party CLI action
+shortTitle: Create a CLI action
 intro: 'Learn how to develop an action to set up a CLI on {% data variables.product.prodname_actions %} runners.'
 redirect_from:
   - /actions/creating-actions/developing-a-third-party-cli-action
   - /actions/sharing-automations/creating-actions/developing-a-third-party-cli-action
+  - /actions/how-tos/sharing-automations/creating-actions/developing-a-third-party-cli-action
 versions:
   fpt: '*'
   ghec: '*'
-type: tutorial
 topics:
   - Actions
 ---
@@ -29,7 +29,7 @@ This article will demonstrate how to write an action that retrieves a specific v
 
 ## Prerequisites
 
-You should have an understanding of how to write a custom action. For more information, see [AUTOTITLE](/actions/creating-actions/about-custom-actions). For a more detailed guide on how to write a custom action, see [AUTOTITLE](/actions/creating-actions/creating-a-javascript-action).
+You should have an understanding of how to write a custom action. For more information, see [AUTOTITLE](/actions/how-tos/creating-and-publishing-actions/managing-custom-actions).
 
 ## Example
 
diff --git a/content/actions/how-tos/creating-and-publishing-actions/index.md b/content/actions/how-tos/creating-and-publishing-actions/index.md
@@ -1,18 +1,18 @@
 ---
-title: Creating actions
-shortTitle: Create actions
+title: Creating and publishing actions
+shortTitle: Create and publish actions
 intro: 'You can create your own actions, use and customize actions shared by the {% data variables.product.prodname_dotcom %} community, or write and share the actions you build.'
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
+redirect_from:
+  - /actions/sharing-automations/creating-actions
+  - /actions/how-tos/sharing-automations/creating-actions
 children:
+  - /managing-custom-actions
+  - /creating-a-third-party-cli-action
   - /setting-exit-codes-for-actions
-  - /releasing-and-maintaining-actions
   - /publishing-actions-in-github-marketplace
-  - /developing-a-third-party-cli-action
-redirect_from:
-  - /actions/sharing-automations/creating-actions
+  - /releasing-and-maintaining-actions
 ---
-
-{% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/content/actions/how-tos/creating-and-publishing-actions/managing-custom-actions.md b/content/actions/how-tos/creating-and-publishing-actions/managing-custom-actions.md
@@ -1,5 +1,6 @@
 ---
 title: Managing custom actions
+shortTitle: Manage custom actions
 intro: 'Learn how to create and manage your own actions, and customize actions shared by the {% data variables.product.prodname_dotcom %} community.'
 versions:
   fpt: '*'
@@ -9,6 +10,8 @@ type: overview
 topics:
   - Action development
   - Fundamentals
+redirect_from:
+  - /actions/how-tos/administering-github-actions/managing-custom-actions
 ---
 
 ## Choosing a location for your action
diff --git a/content/actions/how-tos/creating-and-publishing-actions/publishing-actions-in-github-marketplace.md b/content/actions/how-tos/creating-and-publishing-actions/publishing-actions-in-github-marketplace.md
@@ -7,16 +7,17 @@ redirect_from:
   - /actions/building-actions/publishing-actions-in-github-marketplace
   - /actions/creating-actions/publishing-actions-in-github-marketplace
   - /actions/sharing-automations/creating-actions/publishing-actions-in-github-marketplace
+  - /actions/how-tos/sharing-automations/creating-actions/publishing-actions-in-github-marketplace
 versions:
   fpt: '*'
   ghec: '*'
-type: how_to
 shortTitle: Publish in GitHub Marketplace
 ---
 
-You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}.
+## Prerequisites
 
-## About publishing actions
+>[!NOTE]
+> You must accept the terms of service to publish actions in {% data variables.product.prodname_marketplace %}.
 
 Before you can publish an action, you'll need to create an action in your repository. For more information, see [AUTOTITLE](/actions/creating-actions).
 
diff --git a/content/actions/how-tos/creating-and-publishing-actions/releasing-and-maintaining-actions.md b/content/actions/how-tos/creating-and-publishing-actions/releasing-and-maintaining-actions.md
@@ -2,7 +2,6 @@
 title: Releasing and maintaining actions
 shortTitle: Release and maintain actions
 intro: You can leverage automation and open source best practices to release and maintain actions.
-type: tutorial
 topics:
   - Action development
   - Actions
@@ -14,6 +13,7 @@ versions:
 redirect_from:
   - /actions/creating-actions/releasing-and-maintaining-actions
   - /actions/sharing-automations/creating-actions/releasing-and-maintaining-actions
+  - /actions/how-tos/sharing-automations/creating-actions/releasing-and-maintaining-actions
 ---
 
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/content/actions/how-tos/creating-and-publishing-actions/setting-exit-codes-for-actions.md b/content/actions/how-tos/creating-and-publishing-actions/setting-exit-codes-for-actions.md
@@ -6,11 +6,11 @@ redirect_from:
   - /actions/building-actions/setting-exit-codes-for-actions
   - /actions/creating-actions/setting-exit-codes-for-actions
   - /actions/sharing-automations/creating-actions/setting-exit-codes-for-actions
+  - /actions/how-tos/sharing-automations/creating-actions/setting-exit-codes-for-actions
 versions:
   fpt: '*'
   ghes: '*'
   ghec: '*'
-type: how_to
 ---
  
 {% data reusables.actions.enterprise-github-hosted-runners %}
diff --git a/content/actions/how-tos/index.md b/content/actions/how-tos/index.md
@@ -9,6 +9,7 @@ versions:
 children:
   - /writing-workflows
   - /managing-workflow-runs-and-deployments
+  - /creating-and-publishing-actions
   - /sharing-automations
   - /using-github-hosted-runners
   - /managing-self-hosted-runners
diff --git a/content/actions/how-tos/sharing-automations/index.md b/content/actions/how-tos/sharing-automations/index.md
@@ -14,7 +14,6 @@ redirect_from:
   - /articles/creating-a-github-action
   - /actions/sharing-automations
 children:
-  - /creating-actions
   - /reuse-workflows
   - /creating-workflow-templates-for-your-organization
   - /sharing-actions-and-workflows-from-your-private-repository
diff --git a/content/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on.md b/content/authentication/authenticating-with-single-sign-on/authorizing-a-personal-access-token-for-use-with-single-sign-on.md
@@ -29,6 +29,9 @@ You must authorize your {% data variables.product.pat_v1 %} after creation befor
 
 1. In the dropdown menu, to the right of the organization you'd like to authorize the token for, click **Authorize**.
 
+> [!NOTE]
+> When authorizing a {% data variables.product.pat_v1 %} for use within an organization that belongs to an enterprise which has both an IP allow list and single sign-on enabled at the enterprise level, your IP must also be allowed at the enterprise level. See [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
+
 ## Further reading
 
 * [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)
diff --git a/content/authentication/authenticating-with-single-sign-on/authorizing-an-ssh-key-for-use-with-single-sign-on.md b/content/authentication/authenticating-with-single-sign-on/authorizing-an-ssh-key-for-use-with-single-sign-on.md
@@ -37,6 +37,9 @@ You do not need to authorize SSH certificates signed by your organization's SSH
    ![Screenshot of the "Authentication Keys" section. Next to a key, a dropdown menu, labeled "Configure SSO," is outlined in orange.](/assets/images/help/settings/ssh-sso-button.png)
 1. In the dropdown menu, to the right of the organization you'd like to authorize the SSH key for, click **Authorize**.
 
+> [!NOTE]
+> When authorizing an SSH key for use within an organization that belongs to an enterprise which has both an IP allow list and single sign-on enabled at the enterprise level, your IP must also be allowed at the enterprise level. See [AUTOTITLE](/admin/configuring-settings/hardening-security-for-your-enterprise/restricting-network-traffic-to-your-enterprise-with-an-ip-allow-list).
+
 ## Further reading
 
 * [AUTOTITLE](/authentication/connecting-to-github-with-ssh/checking-for-existing-ssh-keys)
diff --git a/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md b/content/code-security/dependabot/working-with-dependabot/configuring-access-to-private-registries-for-dependabot.md
@@ -33,7 +33,13 @@ For specific ecosystems, you can configure {% data variables.product.prodname_de
 
 ## Configuring private registries
 
-You configure {% data variables.product.prodname_dependabot %}'s access to private registries in the `dependabot.yml` file.
+{% ifversion org-private-registry %}
+
+You can configure {% data variables.product.prodname_dependabot %}'s access to private registries at the org-level. For more information on how to configure that, see [AUTOTITLE](/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries).
+
+{% endif %}
+
+You can also configure {% data variables.product.prodname_dependabot %}'s access to private registries in the `dependabot.yml` file.
 The top-level `registries` key is optional and specifies authentication details.
 
 {% data reusables.dependabot.dependabot-updates-registries %}
diff --git a/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries.md b/content/code-security/securing-your-organization/enabling-security-features-in-your-organization/giving-org-access-private-registries.md
@@ -59,7 +59,7 @@ Any private registries used by the build must also be accessible to the workflow
 
 ## {% data variables.product.prodname_dependabot %} updates access to private registries
 
-{% data variables.product.prodname_dependabot %} uses any private registries defined in the `dependabot.yml` file. It does not have access to the organization-level private registries used by {% data variables.product.prodname_code_scanning %} default setup.
+{% data variables.product.prodname_dependabot %} can use any of the org-level private registries, as well as uses any private registries defined in the `dependabot.yml` file in the repo.
 
 {% data variables.product.prodname_dependabot %} cannot check for security or version updates for code stored in a private registry unless it can access the registry. If you do not configure access to the private registry, then {% data variables.product.prodname_dependabot %} cannot raise pull requests to update any of the dependencies stored in the registry.
 
diff --git a/content/copilot/concepts/content-exclusion-for-github-copilot.md b/content/copilot/concepts/content-exclusion-for-github-copilot.md
@@ -50,7 +50,7 @@ Content exclusions also apply to {% data variables.copilot.copilot_code-review_s
 
 {% data reusables.copilot.content-exclusion-limitations %}
 
-Currently, content exclusions do not apply to symbolic links (symlinks).
+Currently, content exclusions do not apply to symbolic links (symlinks) and repositories located on remote filesystems.
 
 ### Data sent to {% data variables.product.prodname_dotcom %}
 
diff --git a/content/copilot/reference/ai-models/how-copilot-serves-ai-models.md b/content/copilot/reference/ai-models/how-copilot-serves-ai-models.md
@@ -49,4 +49,6 @@ Used for:
 
 {% data variables.product.prodname_copilot %} uses {% data variables.copilot.copilot_gemini_flash %} and {% data variables.copilot.copilot_gemini_25_pro %} hosted on Google Cloud Platform (GCP). When using {% data variables.copilot.copilot_gemini %} models, prompts and metadata are sent to GCP, which makes the [following data commitment](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance): _{% data variables.copilot.copilot_gemini %} doesn't use your prompts, or its responses, as data to train its models._
 
+To provide better service quality and reduce latency, {% data variables.product.github %} uses [prompt caching](https://cloud.google.com/vertex-ai/generative-ai/docs/data-governance#customer_data_retention_and_achieving_zero_data_retention).
+
 When using {% data variables.copilot.copilot_gemini %} models, input prompts and output completions continue to run through {% data variables.product.prodname_copilot %}'s content filters for public code matching, when applied, along with those for harmful or offensive content.
diff --git a/data/reusables/enterprise/repo-policy-rules-preview.md b/data/reusables/enterprise/repo-policy-rules-preview.md
@@ -1 +1,2 @@
 >[!NOTE] Repository policies are currently in {% data variables.release-phases.public_preview %} and subject to change.
+>You can have up to 75 total policies and rulesets per organization, and up to 75 total policies and rulesets per enterprise.
diff --git a/data/reusables/repositories/ruleset-beta-note.md b/data/reusables/repositories/ruleset-beta-note.md
@@ -1,2 +1,2 @@
-> [!NOTE]
-> {% ifversion ghes > 3.16 %}Only changes made to a ruleset after you have upgraded to {% data variables.product.prodname_ghe_server %} 3.17.0, or a later version, are included in the ruleset history.{% endif %}
+> {% ifversion ghes > 3.16 %}[!NOTE]
+> Only changes made to a ruleset after you have upgraded to {% data variables.product.prodname_ghe_server %} 3.17.0, or a later version, are included in the ruleset history.{% endif %}
diff --git a/data/reusables/support/scope-of-support.md b/data/reusables/support/scope-of-support.md
@@ -2,7 +2,8 @@ If your support request is outside of the scope of what our team can help you wi
 
 * Third party integrations, such as Jira{% ifversion ghes %}
 * Hardware setup
-* Hypervisor-related issues, such as OS disk detection, network setup, boot failure, VM console access, etc{% endif %}
+* Hypervisor-related issues, such as OS disk detection, network setup, boot failure, VM console access, etc.
+* Migration assistance between specific hardware platforms or storage providers{% endif %}
 * CI/CD, such as Jenkins
 * Azure DevOps (please contact Azure Support)
 * Writing scripts
diff --git a/package-lock.json b/package-lock.json
diff --git a/src/github-apps/scripts/sync.js b/src/github-apps/scripts/sync.js
@@ -103,11 +103,25 @@ export async function syncGitHubAppsData(openApiSource, sourceSchemas, progAcces
 
             const excludedActors = progActorResources[permissionName]['excluded_actors']
 
-            const additionalPermissions =
-              progAccessData[operation.operationId].permissions.length > 1 ||
-              progAccessData[operation.operationId].permissions.some(
-                (permissionSet) => Object.keys(permissionSet).length > 1,
+            const additionalPermissions = calculateAdditionalPermissions(
+              progAccessData[operation.operationId].permissions,
+            )
+
+            // Filter out metadata permissions when combined with other permissions
+            // The metadata permission is automatically granted with any other repository permission,
+            // so documenting it for operations that require additional permissions is misleading.
+            // This fixes the issue where mutating operations (PUT, DELETE) incorrectly appeared
+            // to only need metadata access when they actually require write permissions.
+            // See: https://github.com/github/docs-engineering/issues/5212
+            if (
+              shouldFilterMetadataPermission(
+                permissionName,
+                progAccessData[operation.operationId].permissions,
               )
+            ) {
+              continue
+            }
+
             // github app permissions
             if (!isActorExcluded(excludedActors, 'server_to_server', actorTypeMap)) {
               const serverToServerPermissions = githubAppsData['server-to-server-permissions']
@@ -332,6 +346,28 @@ function sentenceCase(str) {
   return str.charAt(0).toUpperCase() + str.slice(1)
 }
 
+/**
+ * Calculates whether an operation has additional permissions beyond a single permission.
+ */
+export function calculateAdditionalPermissions(permissionSets) {
+  return (
+    permissionSets.length > 1 ||
+    permissionSets.some((permissionSet) => Object.keys(permissionSet).length > 1)
+  )
+}
+
+/**
+ * Determines whether a metadata permission should be filtered out when it has additional permissions.
+ * Prevents misleading documentation where mutating operations appear to only need metadata access.
+ */
+export function shouldFilterMetadataPermission(permissionName, permissionSets) {
+  if (permissionName !== 'metadata') {
+    return false
+  }
+
+  return calculateAdditionalPermissions(permissionSets)
+}
+
 export function isActorExcluded(excludedActors, actorType, actorTypeMap = {}) {
   if (!excludedActors || !Array.isArray(excludedActors)) {
     return false
@@ -358,7 +394,6 @@ export function isActorExcluded(excludedActors, actorType, actorTypeMap = {}) {
 
   return false
 }
-
 function addAppData(storage, category, data) {
   if (!storage[category]) {
     storage[category] = []
diff --git a/src/github-apps/tests/metadata-permissions.js b/src/github-apps/tests/metadata-permissions.js
