[pull] main from github:main

.github/actions/install-cocofix/action.yml

@@ -0,0 +1,21 @@
+name: Install CocoFix
+
+description: Installs the private package `@github/cocofix` from the GitHub Package Registry.
+
+inputs:
+  token:
+    description: PAT
+    required: true
+
+runs:
+  using: 'composite'
+  steps:
+    - name: Install CoCoFix
+      shell: bash
+      env:
+        TOKEN: ${{ inputs.token }}
+      run: |
+        npm install --no-save \
+          '--@github:registry=https://npm.pkg.github.com' \
+          '--//npm.pkg.github.com/:_authToken=${TOKEN}' \
+          @github/cocofix

.github/workflows/generate-code-scanning-query-lists.yml

@@ -60,6 +60,10 @@ jobs:
           sleep 3
           codeql --version
 
+      - uses: ./.github/actions/install-cocofix
+        with:
+          token: ${{ secrets.DOCS_BOT_PAT_WORKFLOW }}
+
       - name: Build code scanning query list
         run: |
           for lang in "cpp" "csharp" "go" "java" "javascript" "python" "ruby" "swift"; do

.github/workflows/lint-code.yml

@@ -45,5 +45,9 @@ jobs:
       - name: Run Prettier
         run: npm run prettier-check
 
+      - uses: ./.github/actions/install-cocofix
+        with:
+          token: ${{ secrets.DOCS_BOT_PAT_WORKFLOW }}
+
       - name: Run TypeScript
         run: npm run tsc

Dockerfile

@@ -5,7 +5,7 @@
 # --------------------------------------------------------------------------------
 # To update the sha, run `docker pull node:$VERSION-alpine`
 # look for something like: `Digest: sha256:0123456789abcdef`
-FROM node:20-alpine@sha256:c0a3badbd8a0a760de903e00cedbca94588e609299820557e72cba2a53dbaa2c as base
+FROM node:20-alpine@sha256:bf77dc26e48ea95fca9d1aceb5acfa69d2e546b765ec2abfb502975f1a2d4def as base
 
 # This directory is owned by the node user
 ARG APP_HOME=/home/node/app

content/account-and-profile/managing-subscriptions-and-notifications-on-github/setting-up-notifications/configuring-notifications.md

@@ -246,7 +246,7 @@ On the "Notification settings" page, select "Email" or "Web" notifications. Opti
 
 ## Organization alerts notification options
 
-If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", unselect **Email**.
+If you're an organization owner, you'll receive email notifications by default when organization members add new deploy keys to repositories within the organization. You can unsubscribe from these notifications. On the notification settings page, under "Organization alerts", deselect **Email**.
 
 ## Managing your notification settings with {% data variables.product.prodname_mobile %}
 

content/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/about-support-for-actions-runner-controller.md

@@ -25,7 +25,7 @@ If your support request is outside of the scope of what our team can help you wi
 
 - The legacy community-maintained version of ARC
 - Template spec customization
-- Container orchestration, such as Kubernetes setup, networking, etc.
+- Container orchestration, such as Kubernetes setup, networking, building images in ARC (DinD), etc.
 - Applying Kubernetes policies
 - Managed Kubernetes providers or provider-specific configurations
 - [Runner Container Hooks](https://github.com/actions/runner-container-hooks) in conjunction with ARC's `kubernetes` mode

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

@@ -664,38 +664,23 @@ $ ghe-cluster-maintenance -u
 # Unsets maintenance mode
 ```
 
-{% ifversion cluster-node-removal %}
-
-### ghe-remove-node
+{% ifversion cluster-ha-tooling-improvements %}
 
-This utility removes a node from a cluster. If you're replacing a node, after you've set up a replacement node, you can use this command to take the old node offline. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node)."
+### ghe-cluster-repl-bootstrap
 
-You must run this command from the primary MySQL node in your cluster, which is typically the node designated as `mysql-master` in your cluster configuration file (`cluster.conf`). You can use this command to remove any node, with the exception of the `mysql-master` or `redis-master` node. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster#about-the-cluster-configuration-file)."
+This utility configures high availability replication to a secondary set of cluster nodes. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/configuring-high-availability-replication-for-a-cluster)."
 
 ```shell
-ghe-remove-node HOSTNAME
+ghe-cluster-repl-bootstrap
 ```
 
-The command does the following things:
-- Evacuates data from any data services running on the node, so that the remaining nodes in your cluster contain copies of the data
-- Marks the node as offline in your configuration, applies this change to the rest of the nodes in the cluster, and stops traffic being routed to the node
-
-You can run the command with the following flags.
+### ghe-cluster-repl-teardown
 
-Flag | Description
----- | ----------
-`-ne/--no-evacuate` | Skips evacuation of data services (warning: may result in data loss).
-`-v/--verbose` | Prints additional information to the console.
-`-h/--help` | Displays help text for the command.
+This utility disables replication to replica nodes for a cluster in a high availability configuration. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/configuring-high-availability-replication-for-a-cluster#disabling-high-availability-replication-for-a-cluster)."
 
-{% note %}
-
-**Notes:**
-
-- This command can only be used to remove a node from a cluster configuration. It cannot be used to remove a node from a high availability configuration.
-- This command does not support parallel execution. To remove multiple nodes, you must wait until this command has finished before running it for another node.
-
-{% endnote %}
+```shell
+ghe-cluster-repl-teardown
+```
 
 {% endif %}
 
@@ -763,6 +748,41 @@ To evacuate a {% data variables.product.prodname_pages %} storage service before
 ghe-dpages evacuate pages-server-UUID
 ```
 
+{% ifversion cluster-node-removal %}
+
+### ghe-remove-node
+
+This utility removes a node from a cluster. If you're replacing a node, after you've set up a replacement node, you can use this command to take the old node offline. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/replacing-a-cluster-node)."
+
+You must run this command from the primary MySQL node in your cluster, which is typically the node designated as `mysql-master` in your cluster configuration file (`cluster.conf`). You can use this command to remove any node, with the exception of the `mysql-master` or `redis-master` node. For more information, see "[AUTOTITLE](/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initializing-the-cluster#about-the-cluster-configuration-file)."
+
+```shell
+ghe-remove-node HOSTNAME
+```
+
+The command does the following things:
+- Evacuates data from any data services running on the node, so that the remaining nodes in your cluster contain copies of the data
+- Marks the node as offline in your configuration, applies this change to the rest of the nodes in the cluster, and stops traffic being routed to the node
+
+You can run the command with the following flags.
+
+Flag | Description
+---- | ----------
+`-ne/--no-evacuate` | Skips evacuation of data services (warning: may result in data loss).
+`-v/--verbose` | Prints additional information to the console.
+`-h/--help` | Displays help text for the command.
+
+{% note %}
+
+**Notes:**
+
+- This command can only be used to remove a node from a cluster configuration. It cannot be used to remove a node from a high availability configuration.
+- This command does not support parallel execution. To remove multiple nodes, you must wait until this command has finished before running it for another node.
+
+{% endnote %}
+
+{% endif %}
+
 {% ifversion ghe-spokes-deprecation-phase-1 %}
 
 ### ghe-spokesctl

content/admin/identity-and-access-management/reconfiguring-iam-for-enterprise-managed-users/migrating-from-saml-to-oidc.md

@@ -54,9 +54,9 @@ To migrate your enterprise from SAML to OIDC, you will disable your existing {%
 {% data reusables.emus.use-enterprise-recovery-code %}
 {% data reusables.enterprise-accounts.security-tab %}
 1. At the bottom of the page, next to "Migrate to OpenID Connect single sign-on", click **Configure with Azure**.
-1. Read the warning, then click "I understand, begin migrating to OpenID Connect".
+1. Read the warning, then click **I understand, begin migrating to OpenID Connect**.
 {% data reusables.enterprise-accounts.emu-azure-admin-consent %}
-1. After you grant consent, a new browser window will open to {% data variables.location.product_location %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click "Enable OIDC authentication".
+1. After you grant consent, a new browser window will open to {% data variables.location.product_location %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click **Enable OIDC authentication**.
 1. Wait for the migration to complete, which can take up to an hour. To check the status of the migration, navigate to your enterprise's authentication security settings page. If "Require SAML authentication" is selected, the migration is still in progress.
 
    {% warning %}

content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/configuring-high-availability-replication-for-a-cluster.md

@@ -47,11 +47,38 @@ You must assign a static IP address to each new node that you provision, and you
 
 ## Creating a high availability replica for a cluster
 
-- [Assigning active nodes to the primary datacenter](#assigning-active-nodes-to-the-primary-datacenter)
-- [Adding replica nodes to the cluster configuration file](#adding-replica-nodes-to-the-cluster-configuration-file)
-- [Example configuration](#example-configuration)
+{% ifversion cluster-ha-tooling-improvements %}
 
-### Assigning active nodes to the primary datacenter
+To create a high availability replica for your cluster, use the `ghe-cluster-repl-bootstrap` utility, then complete the follow-up tasks that the tool details.
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+1. To begin configuration of high availability, run the following command. The `-p` and `-s` flags are optional. If you're using the flags, replace PRIMARY-DATACENTER and SECONDARY-DATACENTER with the names of your primary and secondary datacenters.
+
+   {% note %}
+
+   **Notes:**
+
+   - By default, the utility will use the name of the primary datacenter in `cluster.conf`.
+   - If no name for the primary datacenter is defined, the utility will use `mona`.
+   - If no name for the secondary datacenter is defined, the utility will use `hubot`.
+
+   {% endnote %}
+
+   ```shell copy
+   ghe-cluster-repl-bootstrap -p PRIMARY-DATACENTER -s SECONDARY-DATACENTER
+   ```
+
+1. After the utility runs, you will see output with further instructions. To finish the configuration, complete the tasks listed in the output.
+
+{% else %}
+
+To create a high availability replica for your cluster, you must complete the following tasks. You can also review an example configuration.
+
+1. [Assign active nodes to the primary datacenter](#1-assign-active-nodes-to-the-primary-datacenter).
+1. [Add replica nodes to the cluster configuration file](#2-add-replica-nodes-to-the-cluster-configuration-file).
+1. [Review an example configuration](#3-review-an-example-configuration).
+
+### 1. Assign active nodes to the primary datacenter
 
 Before you define a secondary datacenter for your replica nodes, ensure that you assign your active nodes to the primary datacenter.
 
@@ -100,7 +127,7 @@ Before you define a secondary datacenter for your replica nodes, ensure that you
 
 After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished assigning your nodes to the cluster's primary datacenter.
 
-### Adding replica nodes to the cluster configuration file
+### 2. Add replica nodes to the cluster configuration file
 
 To configure high availability, you must define a corresponding replica node for every active node in your cluster. To create a new cluster configuration that defines both active and replica nodes, you'll complete the following tasks.
 
@@ -231,7 +258,7 @@ For an example configuration, see "[Example configuration](#example-configuratio
 
 You've finished configuring high availability replication for the nodes in your cluster. Each active node begins replicating configuration and data to its corresponding replica node, and you can direct traffic to the load balancer for the secondary datacenter in the event of a failure. For more information about failing over, see "[AUTOTITLE](/enterprise/admin/enterprise-management/initiating-a-failover-to-your-replica-cluster)."
 
-### Example configuration
+### 3. Review an example configuration
 
 The top-level `[cluster]` configuration should look like the following example.
 
@@ -295,6 +322,8 @@ The configuration for the corresponding replica node in the storage tier should
 ...
 ```
 
+{% endif %}
+
 ## Monitoring replication between active and replica cluster nodes
 
 Initial replication between the active and replica nodes in your cluster takes time. The amount of time depends on the amount of data to replicate and the activity levels for {% data variables.product.prodname_ghe_server %}.
@@ -322,13 +351,28 @@ If you use the original active nodes, after reconfiguring high availability, you
 
 ## Disabling high availability replication for a cluster
 
-You can stop replication to the replica nodes for your cluster deployment of {% data variables.product.prodname_ghe_server %}.
+You can stop replication to the replica nodes for your cluster deployment of {% data variables.product.prodname_ghe_server %}{% ifversion cluster-ha-tooling-improvements %} using the `ghe-cluster-repl-teardown` utility. Alternatively, you can manually disable replication.{% else %}.{% endif %}
+
+{% ifversion cluster-ha-tooling-improvements %}
+
+### Disabling replication using `ghe-cluster-repl-teardown`
+
+{% data reusables.enterprise_clustering.ssh-to-a-node %}
+1. To disable replication, run the following command:
+
+   ```shell copy
+   ghe-cluster-repl-teardown
+   ```
+
+{% data reusables.enterprise_clustering.configuration-finished %}
+
+### Manually disabling replication
+
+{% endif %}
 
 {% data reusables.enterprise_clustering.ssh-to-a-node %}
 {% data reusables.enterprise_clustering.open-configuration-file %}
 1. In the top-level `[cluster]` section, delete the `redis-master-replica`, and `mysql-master-replica` key-value pairs.
 1. Delete each section for a replica node. For replica nodes, `replica` is configured as `enabled`.
 {% data reusables.enterprise_clustering.apply-configuration %}
 {% data reusables.enterprise_clustering.configuration-finished %}
-
-After {% data variables.product.prodname_ghe_server %} returns you to the prompt, you've finished disabling high availability replication.

content/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription.md

@@ -1,6 +1,6 @@
 ---
 title: Connecting an Azure subscription
-intro: "If you use {% data variables.product.product_name %} through a Microsoft Enterprise Agreement, you can enable and pay for usage-based billing on {% data variables.location.product_location %} by connecting an Azure subscription."
+intro: "You can enable and pay for usage-based billing on {% data variables.location.product_location %} by connecting an Azure subscription."
 redirect_from:
   - /github/setting-up-and-managing-your-enterprise/managing-your-enterprise-account/connecting-an-azure-subscription-to-your-enterprise
   - /github/setting-up-and-managing-billing-and-payments-on-github/connecting-an-azure-subscription-to-your-enterprise

content/code-security/codeql-cli/codeql-cli-manual/database-create.md

@@ -94,7 +94,8 @@ The build mode that will be used to create the database.
 Choose your build mode based on the language you are analyzing:
 
 `none`: The database will be created without building the source root.
-Available for JavaScript/TypeScript, Python, Ruby.
+Available for JavaScript/TypeScript, Python, and Ruby. Also available in
+beta for Java.
 
 `autobuild`: The database will be created by attempting to automatically
 build the source root. Available for C/C++, C#, Go, Java/Kotlin, and
@@ -105,7 +106,7 @@ a manually specified build command. Available for C/C++, C#, Go,
 Java/Kotlin, and Swift.
 
 When creating a database with `--command`, there is no need to
-additionally specify '--build-mode none'.
+additionally specify '--build-mode manual'.
 
 Available since `v2.16.4`.
 

content/code-security/codeql-cli/codeql-cli-manual/database-init.md

@@ -107,7 +107,8 @@ The build mode that will be used to create the database.
 Choose your build mode based on the language you are analyzing:
 
 `none`: The database will be created without building the source root.
-Available for JavaScript/TypeScript, Python, Ruby.
+Available for JavaScript/TypeScript, Python, and Ruby. Also available in
+beta for Java.
 
 `autobuild`: The database will be created by attempting to automatically
 build the source root. Available for C/C++, C#, Go, Java/Kotlin, and
@@ -118,7 +119,7 @@ a manually specified build command. Available for C/C++, C#, Go,
 Java/Kotlin, and Swift.
 
 When creating a database with `--command`, there is no need to
-additionally specify '--build-mode none'.
+additionally specify '--build-mode manual'.
 
 Available since `v2.16.4`.
 

content/communities/documenting-your-project-with-wikis/changing-access-permissions-for-wikis.md

@@ -16,7 +16,7 @@ shortTitle: Change access permissions
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under Features, unselect **Restrict editing to collaborators only**.
+1. Under Features, deselect **Restrict editing to collaborators only**.
 
 ## Further reading
 

content/communities/documenting-your-project-with-wikis/disabling-wikis.md

@@ -17,7 +17,7 @@ When you turn off a wiki, the content is hidden, but not erased. If you choose t
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-1. Under Features, unselect **Wikis**.
+1. Under Features, deselect **Wikis**.
 
 ## Further reading