Merge branch 'main' into patch-1

Author: PEliet

.github/workflows/ready-for-doc-review.yml

@@ -29,7 +29,7 @@ jobs:
           owner: github
           # Scope must include every repo that calls this reusable workflow, because
           # the script resolves the PR node (ITEM_NODE_ID) in the calling repo.
-          repositories: docs-internal,docs-content,docs-strategy,docs-early-access,github
+          repositories: docs-internal,docs-content,docs-strategy,docs-early-access,docs-team,github
 
       - name: Check out repo content
         uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0

Dockerfile

@@ -10,7 +10,7 @@
 # ---------------------------------------------------------------
 # To update the sha:
 # https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
-FROM ghcr.io/github/gh-base-image/gh-base-noble:20260708-113537-g661fe65de@sha256:894162a6b21fc03da8ba889760592e6e223ba76f3067723f93bd1e49aff1c46b AS base
+FROM ghcr.io/github/gh-base-image/gh-base-noble:20260713-090615-gb0d388add@sha256:8708e26b53b2304cf8d933be5e8fbca4fa4d07b3ba6e4be238372a5d3029e443 AS base
 
 # Install curl for Node install and determining the early access branch
 # Install git for cloning docs-early-access & translations repos

assets/images/help/code-quality/all-findings-overview-repo.png

@@ -43,7 +43,7 @@ If the new owner of your old username creates a repository with the same name as
 
 ## Links to your previous profile page
 
-After changing your username, links to your previous profile page, such as `https://{% data variables.product.product_url %}/previoususername`, will return a 404 error. We recommend updating any links to your profile from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or Twitter profile{% endif %}.
+After changing your username, links to your previous profile page, such as `https://{% data variables.product.product_url %}/previoususername`, will return a 404 error. We recommend updating any links to your profile from elsewhere{% ifversion fpt or ghec %}, such as your LinkedIn or X (formerly Twitter) profile{% endif %}.
 
 ## Accounts logged in on {% data variables.product.prodname_mobile %}
 

content/account-and-profile/concepts/username-changes.md

@@ -90,7 +90,7 @@ Add pronouns to your public user profile to share information about yourself wit
 You can add up to four links to social accounts on your profile.
 
 {% data reusables.user-settings.access_settings %}
-1. Under "Social accounts", in a blank "Link to social profile" field, type the full URL of the social account. For example, for the `@GitHub` Twitter account, type `https://twitter.com/github`.
+1. Under "Social accounts", in a blank "Link to social profile" field, type the full URL of the social account. For example, for the `@GitHub` X (formerly Twitter) account, type `https://x.com/github`.
 {% data reusables.profile.update-profile %}
 
 {% endif %}

content/account-and-profile/tutorials/personalize-your-profile.md

@@ -679,6 +679,8 @@ To show the full hook payload, result, and any exceptions for the delivery:
 ghe-webhook-logs -g DELIVERY_GUID
 ```
 
+{% ifversion ghes > 3.21 %}
+
 ## Backup and restore
 
 ### ghe-backup-prune-snapshots
@@ -689,8 +691,6 @@ This utility prunes old or invalid backup snapshot directories.
 ghe-backup-prune-snapshots
 ```
 
-{% ifversion ghes > 3.21 %}
-
 ### ghe-backup-healthcheck
 
 This utility quickly confirms that GHES backups are being written, are recent, and that the backup disk is not in a risky state. For example, if usage is 90% or higher, it reports an error because the backup disk may be close to full. Setting `-no-color` gives plain text output, for example in logs or monitoring systems.

content/admin/administering-your-instance/administering-your-instance-from-the-command-line/command-line-utilities.md

@@ -17,8 +17,10 @@ You can configure the following options in the "Backup Service" section of the {
 
 * **Number of snapshots**: Sets how many backup snapshots to retain (default: `10`). Older snapshots are automatically pruned after each successful backup.
 
+{% ifversion ghes > 3.21 %}
 > [!NOTE]
 > You can run the `ghe-backup-prune-snapshots` utility to prune old and invalid snapshots manually.
+{% endif %}
 
 ## Restore options
 

content/admin/backing-up-and-restoring-your-instance/backup-service-settings-reference.md

@@ -120,3 +120,20 @@ Across all of your enterprise's organizations, you can allow or disallow people
 > This policy controls the use of {% data variables.copilot.copilot_autofix_short %} on results found by {% data variables.product.prodname_code_scanning %} security queries only. {% data variables.copilot.copilot_autofix_short %} is an integral part of {% data variables.product.prodname_code_quality %} and cannot be disabled for that feature.
 
 {% endif %}
+
+{% ifversion ai-powered-security-detections %}
+
+## Enforcing a policy to manage the use of AI-powered security detections in your enterprise's repositories
+
+As an enterprise owner, you can control whether organization and repository administrators can enable AI-powered security detections for their organizations and repositories. This policy is set to "Not allowed" by default.
+
+Allowing AI-powered security detections at the enterprise level does not enable the feature. Organization administrators must still explicitly enable AI-powered security detections. Repository administrators can opt-out of the feature.
+
+This policy only takes effect if {% data variables.product.prodname_codeql %} default setup is enabled.
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{% data reusables.enterprise-accounts.policies-tab %}
+{% data reusables.enterprise-accounts.code-security-and-analysis-policies %}
+1. Under "AI Findings", select the dropdown menu and click a policy.
+
+{% endif %}

content/admin/enforcing-policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-code-security-and-analysis-for-your-enterprise.md

@@ -10,6 +10,11 @@ category:
   - Scale your instance
 ---
 
+{% ifversion ghes < 3.21 %}
+> [!NOTE]
+> Support for additional nodes in a high availability configuration is currently in {% data variables.release-phases.public_preview %} and subject to change.
+{% endif %}
+
 For {% data variables.product.prodname_ghe_server %} customers looking to scale horizontally, migrating to and operating a cluster is an option, but is resource-intensive and time-consuming. As an alternative, we recommend adding nodes to an HA configuration.
 
 The terms "additional node" and "stateless node" are used interchangeably throughout this article. Stateless nodes can only be added to HA deployments that contain at least one replica.

content/admin/monitoring-and-managing-your-instance/additional-nodes/configuring-additional-nodes.md

@@ -34,7 +34,7 @@ Like {% data variables.product.prodname_oauth_apps %}, {% data variables.product
 {% data variables.product.prodname_github_apps %} can be installed directly on {% ifversion enterprise-installed-apps %}enterprises, {% endif %}organizations and personal accounts and granted access to specific repositories. They come with built-in webhooks and narrow, specific permissions.
 
 {% ifversion enterprise-apps-public-beta %}
-You can also create an enterprise-owned {% data variables.product.prodname_github_app %} that can only be installed on{% ifversion enterprise-installed-apps %} the enterprise itself or{% endif %} organizations within your enterprise, and can only be authorized by members of your enterprise. For more information, see [AUTOTITLE](/admin/managing-your-enterprise-account/creating-github-apps-for-your-enterprise).
+You can also create an enterprise-owned {% data variables.product.prodname_github_app %} that can only be installed on{% ifversion enterprise-installed-apps %} the enterprise itself or{% endif %} organizations within your enterprise, and can only be authorized by members of your enterprise. For more information, see [AUTOTITLE](/admin/managing-github-apps-for-your-enterprise/creating-github-apps-for-your-enterprise).
 {% endif %}
 
 {% data reusables.apps.app_manager_role %}
@@ -78,7 +78,7 @@ Some examples of automations you could create with a {% data variables.product.p
 
 ### {% data variables.product.prodname_github_apps %} that respond to webhooks
 
-If you want your app to respond to events on {% data variables.product.prodname_dotcom %}, your app should subscribe to webhooks. For example, you may want your app to leave a comment when a pull request is opened. For more information, see [AUTOTITLE](/apps/creating-github-apps/setting-up-a-github-app/using-webhooks-with-github-apps).
+If you want your app to respond to events on {% data variables.product.prodname_dotcom %}, your app should subscribe to webhooks. For example, you may want your app to leave a comment when a pull request is opened. For more information, see [AUTOTITLE](/apps/creating-github-apps/registering-a-github-app/using-webhooks-with-github-apps).
 
 {% ifversion enterprise-installed-apps %}
 Apps installed on enterprises do not currently support webhooks, and must be installed on an organization to receive them.