disable fenced-code-language rule for existing lines

content/actions/creating-actions/creating-a-docker-container-action.md

@@ -107,7 +107,7 @@ Next, the script gets the current time and sets it as an output variable that ac
 {%- else %}
    echo "::set-output name=time::$time"
 {%- endif %}
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
 
    If `entrypoint.sh` executes without any errors, the action's status is set to `success`. You can also explicitly set exit codes in your action's code to provide an action's status. For more information, see "[AUTOTITLE](/actions/creating-actions/setting-exit-codes-for-actions)."
 

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

@@ -488,7 +488,7 @@ Run this utility to add a certificate chain for S/MIME commit signature verifica
 
 Run this utility when {% data variables.location.product_location %} is unable to connect to another server because the latter is using a self-signed SSL certificate or an SSL certificate for which it doesn't provide the necessary CA bundle. One way to confirm this is to run `openssl s_client -connect host:port -verify 0 -CApath /etc/ssl/certs` from {% data variables.location.product_location %}. If the remote server's SSL certificate can be verified, your `SSL-Session` should have a return code of 0, as shown below.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 SSL-Session:
     Protocol  : TLSv1
     Cipher    : AES128-SHA
@@ -503,7 +503,7 @@ SSL-Session:
 
 If, on the other hand, the remote server's SSL certificate can _not_ be verified, your `SSL-Session` should have a nonzero return code:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 SSL-Session:
     Protocol  : TLSv1
     Cipher    : AES128-SHA
@@ -846,7 +846,7 @@ This utility helps to analyze Git traffic. It queries _Governor_ data files, loc
 ghe-governor <subcommand> <column> [options]
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-governor -h
 Usage: ghe-governor [-h] <subcommand> args
 
@@ -917,7 +917,7 @@ ghe-actions-precheck -p [PROVIDER] -cs ["CONNECTION-STRING"]
 
 If your storage system is configured correctly, you'll see the following output.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 All Storage tests passed
 ```
 
@@ -988,7 +988,7 @@ ghe-repl-stop
 
 This utility completely disables replication on an existing replica node, removing the replica configuration. You can run the following command from a replica node, but if the replica node is unreachable, you can also run the command from the primary node.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-repl-teardown
 ```
 

content/admin/backing-up-and-restoring-your-instance/configuring-backups-on-your-instance.md

@@ -80,7 +80,7 @@ Backup snapshots are written to the disk path set by the `GHE_DATA_DIR` data dir
 
 1. To change into the local repository directory, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    cd backup-utils
    ```
 
@@ -130,7 +130,7 @@ You can verify the installation method for {% data variables.product.prodname_en
 {% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
 1. To check if a valid working directory exists inside a Git repository, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git rev-parse --is-inside-work-tree
    ```
 
@@ -167,27 +167,27 @@ To use Git instead of a compressed archive for upgrades, you must back up your e
 {% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
 1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    cp backup.config $HOME/backup.config.saved-$(date +%Y%m%d-%H%M%S)
    ```
 
 1. Change to the local directory on your backup host where you want to install the {% data variables.product.prodname_enterprise_backup_utilities %} Git repository.
 1. To clone the [project repository](https://github.com/github/backup-utils/) to the directory on your backup host, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git clone https://github.com/github/backup-utils.git
    ```
 
 1. To change into the cloned repository, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    cd backup-utils
    ```
 
 {% data reusables.enterprise_backup_utilities.enterprise-backup-utils-update-repo %}
 1. To restore your backup configuration from earlier, copy your existing backup configuration file to the local repository directory. Replace the path in the command with the location of the file saved in step 2.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
    ```
 

content/admin/code-security/managing-supply-chain-security-for-your-enterprise/configuring-dependabot-to-work-with-limited-internet-access.md

@@ -35,7 +35,7 @@ Before configuring {% data variables.product.prodname_dependabot %}, install Doc
 
    For example, to support npm and {% data variables.product.prodname_actions %} you could use the following commands, copying details of the images to load from the `containers.json` file to ensure that you have the correct version and SHA for each image.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    docker pull ghcr.io/github/dependabot-update-job-proxy/dependabot-update-job-proxy:VERSION@SHA
    docker pull ghcr.io/dependabot/dependabot-updater-github-actions:VERSION@SHA
    docker pull ghcr.io/dependabot/dependabot-updater-npm:VERSION@SHA

content/admin/configuration/configuring-user-applications-for-your-enterprise/configuring-email-for-notifications.md

@@ -155,7 +155,7 @@ If you need to verify that your inbound email is functioning, you can review `/v
 
 `/var/log/mail.log` verifies that messages are reaching your server. Here's an example of a successful email reply:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Oct 30 00:47:18 54-171-144-1 postfix/smtpd[13210]: connect from st11p06mm-asmtp002.mac.com[17.172.124.250]
 Oct 30 00:47:19 54-171-144-1 postfix/smtpd[13210]: 51DC9163323: client=st11p06mm-asmtp002.mac.com[17.172.124.250]
 Oct 30 00:47:19 54-171-144-1 postfix/cleanup[13216]: 51DC9163323: message-id=<b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
@@ -169,7 +169,7 @@ Note that the client first connects; then, the queue becomes active. Then, the m
 
 `/var/log/mail-replies/metroplex.log` shows whether inbound emails are being processed to add to issues and pull requests as replies. Here's an example of a successful message:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 [2014-10-30T00:47:23.306 INFO (5284) #] metroplex: processing <b2b9c260-4aaa-4a93-acbb-0b2ddda68579@me.com>
 [2014-10-30T00:47:23.333 DEBUG (5284) #] Matched /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie
 [2014-10-30T00:47:23.334 DEBUG (5284) #] Moving /data/user/mail/reply/new/1414630039.Vfc00I12000eM445784.ghe-tjl2-co-ie => /data/user/incoming-mail/success

content/admin/configuration/configuring-user-applications-for-your-enterprise/configuring-rate-limits.md

@@ -105,13 +105,13 @@ By default, the rate limit for {% data variables.product.prodname_actions %} is
 
 1. To disable the rate limit after it's been enabled, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    ghe-config actions-rate-limiting.enabled false
    ```
 
 1. To apply the configuration, run the following command.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    ghe-config-apply
    ```
 

content/admin/github-actions/advanced-configuration-and-troubleshooting/troubleshooting-github-actions-for-your-enterprise.md

@@ -101,7 +101,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
 
    In the output, find the "Allocated Resources" section. It looks similar to the following example:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    Allocated Resources
    CPU              Memory          Disk
    7740/49600 MHZ   23 GiB/32 GiB   4.4 GiB/7.9 GiB
@@ -127,7 +127,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
    - `actions.hcl.ctmpl`
 1. For the services that you identified that need adjustment, open the corresponding file and locate the `resources` group that looks like the following:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    resources {
      cpu = 512
      memory = 2048
@@ -141,7 +141,7 @@ If any of these services are at or near 100% CPU utilization, or the memory is n
 
    For example, to increase the resource limits in the above example to 1 GHz for the CPU and 4 GB of memory, change it to:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    resources {
      cpu = 1024
      memory = 4096

content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-amazon-s3-storage.md

@@ -64,7 +64,7 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
 
       The command returns a thumbprint in the following format:
 
-      ```
+      ``` <!-- markdownlint-disable-line fenced-code-language -->
       SHA1 Fingerprint=AB:12:34:56:78:90:AB:CD:EF:12:34:56:78:90:AB:CD:EF:12:34:56
       ```
 
@@ -72,7 +72,7 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with a
 
       For example, the thumbprint for the value returned in the previous step is:
 
-      ```
+      ``` <!-- markdownlint-disable-line fenced-code-language -->
       AB1234567890ABCDEF1234567890ABCDEF123456
       ```
 

content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/enabling-github-actions-with-google-cloud-storage.md

@@ -65,13 +65,13 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with G
    - For "Provider name", enter a name for the provider.
    - For "Issuer (URL)", enter the following URL, replacing `HOSTNAME` with the public hostname for {% data variables.location.product_location_enterprise %}:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      https://HOSTNAME/_services/token
      ```
 
      For example:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      https://my-ghes-host.example.com/_services/token
      ```
 
@@ -83,13 +83,13 @@ To configure {% data variables.product.prodname_ghe_server %} to use OIDC with G
    - Under "Attribute Conditions", click **Add condition**.
    - For "Condition CEL", enter the following condition, replacing `HOSTNAME` with the public hostname for {% data variables.location.product_location_enterprise %}:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      google.subject == "HOSTNAME"
      ```
 
      For example:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      google.subject == "my-ghes-host.example.com"
      ```
 

content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/managing-self-hosted-runners-for-dependabot-updates.md

@@ -52,7 +52,7 @@ The CPU and memory requirements will depend on the number of concurrent runners
 
 If you specify more than 14 concurrent runners on a VM, you must also update the Docker `/etc/docker/daemon.json` configuration to increase the default number of networks Docker can create.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {
   "default-address-pools": [
     {"base":"10.10.0.0/16","size":24}

content/admin/github-actions/managing-access-to-actions-from-githubcom/setting-up-the-tool-cache-on-self-hosted-runners-without-internet-access.md

@@ -80,7 +80,7 @@ You can populate the runner tool cache by running a {% data variables.product.pr
 
     After extracting the tool cache artifact uploaded in the above example, you should have a directory structure on your self-hosted runner that is similar to the following example:
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     RUNNER_DIR
     ├── ...
     └── _work

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/troubleshooting-saml-authentication.md

@@ -67,11 +67,11 @@ The message typically indicates that the person's username or email address has
 
 If the `Recipient` does not match the ACS URL for {% data variables.location.product_location %}, one of the following two error messages will appear in the authentication log when a user attempts to authenticate.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Recipient in the SAML response must not be blank.
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Recipient in the SAML response was not valid.
 ```
 
@@ -81,7 +81,7 @@ Ensure that you set the value for `Recipient` on your IdP to the full ACS URL fo
 
 If your IdP does not sign the SAML response, or the signature does not match the contents, the following error message will appear in the authentication log.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 SAML Response is not signed or has been modified.
 ```
 
@@ -91,7 +91,7 @@ Ensure that you configure signed assertions for the {% data variables.product.pr
 
 If the IdP's response has a missing or incorrect value for `Audience`, the following error message will appear in the authentication log.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Audience is invalid. Audience attribute does not match https://YOUR-INSTANCE-URL
 ```
 

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/exporting-audit-log-activity-for-your-enterprise.md

@@ -42,6 +42,6 @@ You can also export Git events data by date range.
 1. Click {% octicon "file-zip" aria-hidden="true" %} **Download Results**.
 1. The data is exported as a compressed JSON file. To extract the JSON data, uncompress the file using an archive utility client or command. For example:
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     gunzip export-avocado-corp-1642896556.json.gz
     ```

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/identifying-audit-log-events-performed-by-an-access-token.md

@@ -58,7 +58,7 @@ Then, include `hashed_token:"VALUE"` in your search phrase, replacing VALUE with
 
 For example, if the name of the enterprise account is `octo-corp`, the following curl command would search @octo-corp's audit log for all events that are associated with the token whose URI-encoded SHA-256 hash is `EH4L8o6PfCqipALbL%2BQT62lyqUtnI7ql0SPbkaQnjv8`.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 curl --header "Accept: application/vnd.github+json" --header "Authorization: Bearer YOUR-TOKEN" {% data reusables.rest-api.version-header %} 'https://api.github.com/enterprises/octo-corp/audit-log?phrase=hashed_token:"EH4L8o6PfCqipALbL%2BQT62lyqUtnI7ql0SPbkaQnjv8"'
 ```
 

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

@@ -111,7 +111,7 @@ For information on creating or accessing your access key ID and secret key, see
    - Add the permissions policy you created above to allow writes to the bucket.
    - Edit the trust relationship to add the `sub` field to the validation conditions, replacing `ENTERPRISE` with the name of your enterprise.
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      "Condition": {
         "StringEquals": {
            "oidc-configuration.audit-log.githubusercontent.com:aud": "sts.amazonaws.com",

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/using-the-audit-log-api-for-your-enterprise.md

@@ -48,7 +48,7 @@ curl -H "Authorization: Bearer TOKEN" \
 
 The query below searches for audit log events created on Jan 1st, 2022 in the `avocado-corp` enterprise, and returns the first page with a maximum of 100 items per page using pagination. For more information about pagination, see "[AUTOTITLE](/rest/guides/using-pagination-in-the-rest-api)." The `--include` flag causes the headers to be returned along with the response.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 curl --include -H "Authorization: Bearer TOKEN" \
 --request GET \
 "https://api.github.com/enterprises/avocado-corp/audit-log?phrase=created:2022-01-01&per_page=100"
@@ -56,7 +56,7 @@ curl --include -H "Authorization: Bearer TOKEN" \
 
 If there are more than 100 results, the `link` header will include URLs to fetch the next, first, and previous pages of results.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 link: <https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=MS42NjQzODMzNTk5MjdlKzEyfDloQzBxdURzaFdVbVlLWjkxRU9mNXc%3D&before=>; rel="next",
 <https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=>; rel="first",
 <https://api.github.com/enterprises/13827/audit-log?%3A2022-11-01=&per_page=100&after=&before=MS42Njc4NDA2MjM4MzNlKzEyfExqeG5sUElvNEZMbG1XZHA5akdKTVE%3D>; rel="prev"

content/admin/monitoring-managing-and-updating-your-instance/caching-repositories/configuring-a-repository-cache.md

@@ -24,7 +24,7 @@ To have your CI machines fetch from the repository cache instead of the primary
 
 For example, the global `.gitconfig` for the CI machine would include these lines.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 [url "https://europe-ci.github.example.com/"]
 	insteadOf = https://github.example.com/
 ```
@@ -52,7 +52,7 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
 
    - If you're configuring a repository cache in addition to one or more existing replicas, use the `-a` or `--add` argument.
 
-      ```
+      ``` <!-- markdownlint-disable-line fenced-code-language -->
       ghe-repl-setup -a PRIMARY-IP
       ```
 1. To configure the repository cache, use the `ghe-repl-node` command and include the necessary parameters.
@@ -60,7 +60,7 @@ Then, when told to fetch `https://github.example.com/myorg/myrepo`, Git will ins
     - Set a `cache-domain` for the repository cache, replacing _EXTERNAL-CACHE-DOMAIN_ with the hostname Git clients will use to access the repository cache. If you do not specify a `cache-domain`, {% data variables.product.product_name %} will prepend the _CACHE-LOCATION_ value as a subdomain to the hostname configured for your instance. For more information, see "[AUTOTITLE](/admin/configuration/configuring-network-settings/configuring-a-hostname)."
     - If you haven't already, set the datacenter name on the primary and any replica appliances, replacing DC-NAME with a datacenter name.
 
-      ```
+      ``` <!-- markdownlint-disable-line fenced-code-language -->
       ghe-repl-node --datacenter DC-NAME
       ```
 
@@ -88,19 +88,19 @@ Data location policies affect only Git content. Content in the database, such as
 
 You can configure a policy to replicate all networks with the `--default` flag. For example, this command will create a policy to replicate a single copy of every repository network to the set of repository caches whose `cache_location` is "kansas".
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-spokesctl cache-policy set --default 1 kansas
 ```
 
 To configure replication for a repository network, specify the repository that is the root of the network. A repository network includes a repository and all of the repository's forks. You cannot replicate part of a network without replicating the whole network.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-spokesctl cache-policy set <owner/repository> 1 kansas
 ```
 
 You can override a policy that replicates all networks and exclude specific networks by specifying a replica count of zero for the network. For example, this command specifies that any repository cache in location "kansas" cannot contain any copies of that network.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-spokesctl cache-policy set <owner/repository> 0 kansas
 ```
 

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

@@ -89,7 +89,7 @@ Before you define a secondary datacenter for your replica nodes, ensure that you
 
     **Note**: If you changed the name of the primary datacenter in step 3, find the `consul-datacenter` key-value pair in the section for each node and change the value to the renamed primary datacenter. For example, if you named the primary datacenter `primary`, use the following key-value pair for each node.
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     consul-datacenter = primary
     ```
 
@@ -122,19 +122,19 @@ For an example configuration, see "[Example configuration](#example-configuratio
 {% data reusables.enterprise_clustering.ssh-to-a-node %}
 1. Back up your existing cluster configuration.
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     cp /data/user/common/cluster.conf ~/$(date +%Y-%m-%d)-cluster.conf.backup
     ```
 
 1. Create a copy of your existing cluster configuration file in a temporary location, like `/home/admin/cluster-replica.conf`.
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     grep -Ev "(?:|ipv|uuid)" /data/user/common/cluster.conf > ~/cluster-replica.conf
     ```
 
 1. Remove the `[cluster]` section from the temporary cluster configuration file that you copied in the previous step.
 
-    ```
+    ``` <!-- markdownlint-disable-line fenced-code-language -->
     git config -f ~/cluster-replica.conf --remove-section cluster
     ```
 

content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/initiating-a-failover-to-your-replica-cluster.md

@@ -34,7 +34,7 @@ To fail over to replica nodes, you must have configured high availability replic
 
     ```shell
   ghe-cluster-failover
-  ```
+  ``` <!-- markdownlint-disable-line fenced-code-language -->
 
 {% data reusables.enterprise_clustering.configuration-finished %}
 1. Update the DNS record to point to the IP address of the load balancer for your replica cluster. After the TTL period expires, requests will be directed to the replica cluster.

content/admin/monitoring-managing-and-updating-your-instance/configuring-clustering/monitoring-the-health-of-your-cluster.md

@@ -113,7 +113,7 @@ You can configure [Nagios](https://www.nagios.org/) to monitor {% data variables
 
    **Example definition**
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    define command {
         command_name    check_ssh_ghe_cluster
         command_line    $USER1$/check_by_ssh -H $HOSTADDRESS$ -C "ghe-cluster-status -n" -l admin -p 122 -t 30
@@ -124,7 +124,7 @@ You can configure [Nagios](https://www.nagios.org/) to monitor {% data variables
 
    **Example definition**
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    define host{
         use                     generic-host
         host_name               ghe-data-node-0

content/admin/monitoring-managing-and-updating-your-instance/configuring-high-availability/creating-a-high-availability-replica.md

@@ -110,7 +110,7 @@ Configure Geo DNS using the IP addresses of the primary and replica nodes. You c
 
 For testing, you can add entries to the local workstation's `hosts` file (for example, `/etc/hosts`). These example entries will resolve requests for `HOSTNAME` to `replica2`. You can target specific hosts by commenting out different lines.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 # <primary IP>      HOSTNAME
 # <replica1 IP>     HOSTNAME
 <replica2 IP>     HOSTNAME

content/admin/monitoring-managing-and-updating-your-instance/configuring-high-availability/monitoring-a-high-availability-configuration.md

@@ -84,7 +84,7 @@ If you've recently configured high availability or geo-replication, the initial
 
 You can view a specific repository's replication status by connecting to a node and running the following {% ifversion ghe-spokes-deprecation-phase-1 %}commands{% else %}command{% endif %}, replacing OWNER with the repository's owner and REPOSITORY with the repository's name.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {%- ifversion ghe-spokes-deprecation-phase-1 %}
 ghe-spokesctl check OWNER/REPOSITORY
 ghe-spokesctl info OWNER/REPOSITORY
@@ -95,7 +95,7 @@ ghe-spokes diagnose OWNER/REPOSITORY
 
 Alternatively, if you want to view a repository network's replication status, replace NETWORK-ID/REPOSITORY-ID with the network ID and repository ID number.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {%- ifversion ghe-spokes-deprecation-phase-1 %}
 ghe-spokesctl check NETWORK-ID/REPOSITORY-ID
 ghe-spokesctl info NETWORK-ID/REPOSITORY-ID
@@ -108,7 +108,7 @@ ghe-spokes diagnose NETWORK-ID/REPOSITORY-ID
 
 You can view a specific storage object's status by connecting to a node and running the following command, replacing OID with the object's ID.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ghe-storage info OID
 ```
 

content/admin/monitoring-managing-and-updating-your-instance/monitoring-your-instance/about-system-logs.md

@@ -49,13 +49,13 @@ All entries from the `audit.log` file use and can be filtered with the `github_a
 
 For example, this entry shows that a new repository was created.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Oct 26 01:42:08 github-ent github_audit: {:created_at=>1351215728326, :actor_ip=>"10.0.0.51", :data=>{}, :user=>"some-user", :repo=>"some-user/some-repository", :actor=>"some-user", :actor_id=>2, :user_id=>2, :action=>"repo.create", :repo_id=>1, :from=>"repositories#create"}
 ```
 
 This example shows that commits were pushed to a repository.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Oct 26 02:19:31 github-ent github_audit: { "pid":22860, "ppid":22859, "program":"receive-pack", "git_dir":"/data/repositories/some-user/some-repository.git", "hostname":"github-ent", "pusher":"some-user", "real_ip":"10.0.0.51", "user_agent":"git/1.7.10.4", "repo_id":1, "repo_name":"some-user/some-repository", "transaction_id":"b031b7dc7043c87323a75f7a92092ef1456e5fbaef995c68", "frontend_ppid":1, "repo_public":true, "user_name":"some-user", "user_login":"some-user", "frontend_pid":18238, "frontend":"github-ent", "user_email":"some-user@github.example.com", "user_id":2, "pgroup":"github-ent_22860", "status":"post_receive_hook", "features":" report-status side-band-64k", "received_objects":3, "receive_pack_size":243, "non_fast_forward":false, "current_ref":"refs/heads/main" }
 ```
 

content/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server.md

@@ -267,7 +267,7 @@ To upgrade an instance that comprises multiple nodes using an upgrade package, y
 
    **Note:** While the resync is in progress `ghe-repl-status` may indicate that replication is behind. For example, you may see the following message.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    CRITICAL: git replication is behind the primary by more than 1007 repositories and/or gists
    ```
 

content/admin/packages/quickstart-for-configuring-your-minio-storage-bucket-for-github-packages.md

@@ -122,7 +122,7 @@ For more information about your options, see the official [MinIO docs](https://d
 
 To finish configuring storage for {% data variables.product.prodname_registry %}, you'll need to copy the MinIO storage URL:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 echo "http://${MINIO_ACCESS_KEY}:${MINIO_SECRET_KEY}@minioclustername.example.com:9000"
 ```
 

content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-repository-management-policies-in-your-enterprise.md

@@ -289,7 +289,7 @@ Enabling anonymous Git read access allows users to bypass authentication for cus
 
 Anonymous Git read access is disabled by default.{% ifversion ghes = 3.6 or ghes = 3.7 %} When you upgrade to {% data variables.product.product_name %} 3.6 or later, anonymous Git read access is automatically disabled at the application level, and `git://` connections on port 9418 will return the following error.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 The unauthenticated git protocol on port 9418 is no longer supported.
 ```
 

content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-environment.md

@@ -27,7 +27,7 @@ You can use a Linux container management tool to build a pre-receive hook enviro
 {% data reusables.linux.ensure-docker %}
 1. Create the file `Dockerfile.alpine` that contains this information:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    FROM alpine:latest
    RUN apk add --no-cache git bash
    ```

content/admin/policies/enforcing-policy-with-pre-receive-hooks/creating-a-pre-receive-hook-script.md

@@ -25,7 +25,7 @@ A pre-receive hook script executes in a pre-receive hook environment on {% data
 
 After a push occurs and before any refs are updated for the remote repository, the `git-receive-pack` process on {% data variables.location.product_location %} invokes the pre-receive hook script. Standard input for the script, `stdin`, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 <old-value> SP <new-value> SP <ref-name> LF
 ```
 
@@ -180,7 +180,7 @@ You can test a pre-receive hook script locally before you create or update it on
 
 1. Create a test pre-receive script called `always_reject.sh`. This example script will reject all pushes, which is useful for locking a repository:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    #!/usr/bin/env bash
 
    echo "error: rejecting all pushes"

content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md

@@ -264,7 +264,7 @@ This would result in a '.npmrc' with the registry:
 
 {% raw %}
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 @<org-name>:registry=https://<private-registry-url>/<org-name>
 ```
 

content/code-security/supply-chain-security/understanding-your-software-supply-chain/configuring-dependency-review.md

@@ -154,7 +154,7 @@ Notice that all of the examples use a short version number for the action (`v3`)
            fail-on-scopes: development, runtime
   {% endif %}
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
 ### Using a configuration file to set up {% data variables.dependency-review.action_name %}
 
 1. Add a new YAML workflow to your `.github/workflows` folder and use `config-file` to specify that you are using a configuration file.

content/contributing/collaborating-on-github-docs/using-git-on-github-docs.md

@@ -17,26 +17,26 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
 1. In the terminal, change the current working directory to the location where you cloned the documentation repository. For example:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    cd ~/my-cloned-repos/docs
    ```
 
 1. Switch to the default branch: `main`.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git checkout main
    ```
 
 1. Get the most recent commits from the remote repository.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git pull origin main
    ```
 
 1. Switch to or create a topic branch.
    - To start a new project, create a new topic branch from `main`.
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git checkout -b YOUR-TOPIC-BRANCH
      ```
 
@@ -44,7 +44,7 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
      **Note**: You can use forward slashes as part of the branch name, for example to include your user name:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git checkout -b my-username/new-codespace-policy
      ```     
 
@@ -52,7 +52,7 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
    - To work on an existing project, switch to your topic branch and merge changes from `main`.
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git checkout YOUR-TOPIC-BRANCH
      git merge main
      ```
@@ -65,7 +65,7 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
 1. When you're ready to commit your changes, open a terminal and check the status of your topic branch with `git status`. Make sure you see the correct set of changes.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git status
    On branch YOUR-TOPIC-BRANCH
 
@@ -84,7 +84,7 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
    - If you created new files or updated existing files, use `git add FILENAME [FILENAME...]`. For example:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git add example-new-file.md example-changed-file.md
      ```
 
@@ -92,13 +92,13 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
    - If you deleted files, use `git rm FILENAME [FILENAME...]`. For example:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git rm example-deleted-file.md
      ```
 
 1. Commit your changes.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git commit -m "Commit message title (max 72 characters)
    
    Optional fuller description of what changed (no character limit). 
@@ -114,13 +114,13 @@ To keep your local branches in sync with their remotes and avoid merge conflicts
 
    - The first time you push your branch you can choose to add an upstream tracking branch. This allows you to use `git pull` and `git push` on that branch without additional arguments.
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git push --set-upstream origin YOUR-TOPIC-BRANCH
      ```
 
    - If you've pushed this branch before, and set an upstream tracking branch you can use:
 
-     ```
+     ``` <!-- markdownlint-disable-line fenced-code-language -->
      git push
      ```
 
@@ -152,7 +152,7 @@ There are two ways to handle merge conflicts:
 1. Open the first of these files in your text editor.
 1. In the file, look for the merge conflict markers.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    <<<<<<< HEAD
    Here are the changes you've made.
    =====================
@@ -162,7 +162,7 @@ There are two ways to handle merge conflicts:
 
 1. Decide which changes to keep and delete the unwanted changes and the merge conflict markers. If you need to make further changes, you can do so at the same time. For example, you could change the five lines shown in the previous code sample to the single line:
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    Here are the changes you want to use.
    ```
 
@@ -176,19 +176,19 @@ There are two ways to handle merge conflicts:
 
 1. In the terminal, stage the file, or files, that you just modified.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git add changed-file-1.md changed-file-2.md
    ```
 
 1. Commit the files.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git commit -m "Resolves merge conflicts"
    ```
 
 1. Push the committed changes to the remote repository on {% data variables.product.prodname_dotcom_the_website %}.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    git push
    ```
 

content/contributing/setting-up-your-environment-to-work-on-github-docs/troubleshooting-your-environment.md

@@ -18,7 +18,7 @@ If a staging deployment is pending for more than ten minutes, try closing your p
 
 If that doesn't work, use the commands below to trigger a new staging deployment by pushing an empty commit on the command line.
   
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 git commit --allow-empty -m 'empty commit to redeploy staging'
 git push
 ```
@@ -27,7 +27,7 @@ git push
 
 If your tests are stuck on "In progress" or "Pending" for more than an hour, use the commands below to rerun CI by pushing an empty commit on the command line.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 git commit --allow-empty -m 'empty commit to rerun CI'
 git push
 ```
@@ -36,13 +36,13 @@ git push
 
 If you are running `script/server` and get a `Cannot find module` error, try the following command before restarting the server.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 npm install
 ```
 
 If that doesn't fix the problem, use the following command to remove the `node_modules` directory and reinstall.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 rm -rf node_modules
 npm install
 ```
@@ -51,7 +51,7 @@ npm install
 
 If you are having trouble with the staging server, you should see more information about the error in your browser or on the command line if you run the site locally. Check out your branch locally and use the following command to launch the local server.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 script/server
 ```
 
@@ -59,7 +59,7 @@ When the server is running, navigate to the problematic article on `https://loca
 
 If you see an error resembling the one below, make sure single quotes are properly escaped in the frontmatter. Also, check the formatting in `redirect_from` blocks. For more information, see "[AUTOTITLE](/contributing/syntax-and-versioning-for-github-docs/using-yaml-frontmatter#escaping-single-quotes)."
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 error parsing file: /Users/z/git/github/docs/content/dotcom/articles/troubleshooting-custom-domains-and-github-pages.md
 (node:89324) UnhandledPromiseRejectionWarning: YAMLException: can not read a block mapping entry; a multiline key may not be an implicit key at line 4, column 14:
     redirect_from:
@@ -76,7 +76,7 @@ When you locate the broken link, make sure the link is versioned correctly. For
 
 If an article that is available for {% data variables.product.prodname_ghe_server %} links to a {% data variables.product.prodname_dotcom_the_website %}-only article, include the version in the path to prevent the URL from automatically converting to include a {% data variables.product.prodname_ghe_server %} version number. The following example demonstrates how to link from a {% data variables.product.prodname_ghe_server %} article to a {% data variables.product.prodname_dotcom_the_website %}-only article.
   
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 [{% raw %}{{ data variables.product.prodname_github_connect }} Addendum to the {{ data variables.product.prodname_enterprise }} License Agreement{% endraw %}](/free-pro-team@latest/articles/github-connect-addendum-to-the-github-enterprise-license-agreement/)"
 ```
 

content/contributing/syntax-and-versioning-for-github-docs/using-markdown-and-liquid-in-github-docs.md

@@ -55,7 +55,7 @@ For information on when to use callout tags, see "[AUTOTITLE](/contributing/writ
 
 ### Example usage of a callout
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% note %}
 
 **Note:** Owners and administrators can add outside collaborators to a repository.
@@ -163,7 +163,7 @@ We occasionally need to write documentation for different operating systems. Eac
 
 ### Example usage of operating system tags
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% mac %}
 
 These instructions are pertinent to Mac users.
@@ -171,7 +171,7 @@ These instructions are pertinent to Mac users.
 {% endmac %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% linux %}
 
  These instructions are pertinent to Linux users.
@@ -179,7 +179,7 @@ These instructions are pertinent to Mac users.
 {% endlinux %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% windows %}
 
 These instructions are pertinent to Windows users.
@@ -199,7 +199,7 @@ You can define a default tool for an article in the YAML frontmatter. For more i
 
 ### Example usage of tool tags
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% api %}
 
 These instructions are pertinent to API users.
@@ -207,7 +207,7 @@ These instructions are pertinent to API users.
 {% endapi %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% bash %}
 
 These instructions are pertinent to Bash shell commands.
@@ -215,7 +215,7 @@ These instructions are pertinent to Bash shell commands.
 {% endbash %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% cli %}
 
 These instructions are pertinent to GitHub CLI users.
@@ -223,7 +223,7 @@ These instructions are pertinent to GitHub CLI users.
 {% endcli %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% codespaces %}
 
 These instructions are pertinent to Codespaces users. They are mostly used outside the Codespaces docset, when we want to refer to how to do something inside Codespaces. Otherwise `webui` or `vscode` may be used.
@@ -231,7 +231,7 @@ These instructions are pertinent to Codespaces users. They are mostly used outsi
 {% endcodespaces %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% curl %}
 
 These instructions are pertinent to curl commands.
@@ -239,7 +239,7 @@ These instructions are pertinent to curl commands.
 {% endcurl %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% desktop %}
 
  These instructions are pertinent to GitHub Desktop.
@@ -247,7 +247,7 @@ These instructions are pertinent to curl commands.
 {% enddesktop %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% importer_cli %}
 
 These instructions are pertinent to GitHub Enterprise Importer CLI users.
@@ -255,7 +255,7 @@ These instructions are pertinent to GitHub Enterprise Importer CLI users.
 {% endimporter_cli %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% javascript %}
 
 These instructions are pertinent to javascript users.
@@ -263,7 +263,7 @@ These instructions are pertinent to javascript users.
 {% endjavascript %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% jetbrains %}
 
 These instructions are pertinent to users of JetBrains IDEs.
@@ -271,7 +271,7 @@ These instructions are pertinent to users of JetBrains IDEs.
 {% endjetbrains %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% powershell %}
 
 These instructions are pertinent to `pwsh` and `powershell` commands.
@@ -279,7 +279,7 @@ These instructions are pertinent to `pwsh` and `powershell` commands.
 {% endpowershell %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% vscode %}
 
 These instructions are pertinent to VS Code users.
@@ -287,7 +287,7 @@ These instructions are pertinent to VS Code users.
 {% endvscode %}{% endraw %}
 ```
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% webui %}
 
 These instructions are pertinent to GitHub UI users.
@@ -307,7 +307,7 @@ If you create a table where the first column contains headers for the table rows
 
 ### Example table with row headers
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% rowheaders %}
 
 |             | Mona | Tom    | Hobbes |
@@ -320,7 +320,7 @@ If you create a table where the first column contains headers for the table rows
 
 ### Example table without row headers
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 | Name   | Vocation         |
 | ------ | ---------------- |
 | Mona   | GitHub mascot    |
@@ -354,15 +354,15 @@ The links to Markdown pages undergo some transformations on the server side to m
 
 For example, if you include the following link in a content file:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 /github/writing-on-github/creating-a-saved-reply
 ```
 When viewed on {% data variables.product.prodname_dotcom_the_website %} docs, the link gets rendered with the language code:
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 /en/github/writing-on-github/creating-a-saved-reply
 ```
 and when viewed on {% data variables.product.prodname_ghe_server %} docs, the version is included as well:
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 /en/enterprise-server@2.20/github/writing-on-github/creating-a-saved-reply
 ```
 For more information about links, see "[AUTOTITLE](/contributing/writing-for-github-docs/style-guide#links)."

content/contributing/syntax-and-versioning-for-github-docs/versioning-documentation.md

@@ -144,13 +144,13 @@ The Liquid operators `==`, `>=`, and `<=` are not supported in the {% data varia
 
 When all operands must be true for the condition to be true, use the operator `and`:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% ifversion ghes > 2.21 and ghes < 3.1 %}{% endraw %}
 ```
 
 When at least one operand must be true for the condition to be true, use the operator `or`:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% ifversion fpt or ghes > 2.21 %}{% endraw %}
 ```
 
@@ -162,13 +162,13 @@ When using Liquid conditionals in lists or tables, you can use [whitespace contr
 
 You can add a hyphen (`-`) on either the left, right, or both sides to indicate that there should be no newline or other whitespace on that side.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{%- ifversion fpt %}{% endraw %}
 ```
 
 For example, to version a table row, instead of adding liquid versioning for the row starting at the end of the previous row, like this:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Column A | Column B | Column C
 ---------|----------|---------
 This row is for all versions | B1 | C1{% raw %}{% ifversion ghes %}{% endraw %}
@@ -178,7 +178,7 @@ This row is for all versions | B3 | C3
 
 You can include the liquid versioning on its own line and use whitespace control to strip the newline to the left of the liquid tag. This makes reading the source much easier, without breaking the rendering of the table:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Column A | Column B | Column C
 ---------|----------|---------
 This row is for all versions | B1 | C1

content/contributing/writing-for-github-docs/content-model.md

@@ -573,7 +573,7 @@ Further reading sections highlight additional targeted articles that aren’t al
 - Use further reading sections sparingly and when they provide high value - see style guide for guidelines on linking.
 
 #### Title and format for further reading sections
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ### Further reading
 - "[Article title](article-URL)”
 - [External resource title](external-resource-URL) in External Resource Name

content/contributing/writing-for-github-docs/style-guide.md

@@ -74,7 +74,7 @@ Only include a CTA button if navigating to the link supports user needs. Do not
 
 Style your CTAs using the following format.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}<a href="https://github.com/DESTINATION/URL" target="_blank" class="btn btn-primary mt-3 mr-3 no-underline"><span>Try PRODUCT NAME</span> {% octicon "link-external" height:16 %}</a>{% endraw %}
 ```
 
@@ -115,7 +115,7 @@ Use inline code blocks to refer to short command names.
 Use command blocks for longer or more complex commands.
 - **Use:** Enable maintenance mode according to your scheduled window by connecting to the administrative shell of any cluster node and running:
 
-  ```
+  ``` <!-- markdownlint-disable-line fenced-code-language -->
   ghe-cluster-maintenance -s
   ```
 
@@ -126,7 +126,7 @@ Avoid inline links in command names.
 When code examples refer to a larger file, show the relevant section of the file, so that users understand how to edit their own code in context.
 - **Use:**
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 on:
   schedule:
     - cron:  "40 19 * * *"
@@ -134,7 +134,7 @@ on:
 
 - **Avoid:**
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 schedule:
   - cron:  "40 19 * * *"
 ```
@@ -375,7 +375,7 @@ At the end of the article containing MIT-licensed content
 
 This text is only an example. Always use the license text from the project you are attributing.
 
-`````
+````` <!-- markdownlint-disable-line fenced-code-language -->
 ## Legal notice
 
 Portions have been adapted from [PROJECT](/LINK/TO/PROJECT) under the MIT license:
@@ -434,7 +434,7 @@ Sometimes, you need to link from one version of GitHub Docs to another. When you
 
 For example, the Free, Pro, & Team version of "[AUTOTITLE](/organizations/managing-organization-settings/managing-the-publication-of-github-pages-sites-for-your-organization)" might link to the {% data variables.product.prodname_ghe_cloud %} version of the same article like this:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 You can choose to allow or disallow the publication of GitHub Pages sites.
 
 Organizations that use G{% data variables.product.prodname_ghe_cloud %} can choose to allow publicly published sites, privately published sites, both, or neither. For more information, see [the GitHub Enterprise Cloud documentation](/enterprise-cloud@latest/{{ currentArticle }}).
@@ -442,13 +442,13 @@ Organizations that use G{% data variables.product.prodname_ghe_cloud %} can choo
 
 To link to a different article in a different version, use this format:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see "[ARTICLE TITLE](/)" in the VERSION documentation.
 ```
 
 To link to the same article in a different version, use this format:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see [the VERSION documentation](/VERSION/{{ currentArticle }}).
 ```
 
@@ -460,18 +460,18 @@ When we link to specific sections of articles, we want to make sure the link is
 
 To link to a specific header in the same article, use this format:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see "[HEADER TITLE](#HEADER-TITLE)."
 ```
 
 To link to a specific header in a different article, use this format:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see "[AUTOTITLE](PATH-TO-ARTICLE#HEADER-TITLE)."
 ```
 
 To link to two or more specific headers in a different article, use this format:
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see "[HEADER-TITLE-1](PATH-TO-ARTICLE#SECTION-LINK-1)" and "[HEADER-TITLE-2](PATH-TO-ARTICLE#SECTION-LINK-2)" in "ARTICLE-TITLE."
 ```
 
@@ -479,7 +479,7 @@ For more information, see "[HEADER-TITLE-1](PATH-TO-ARTICLE#SECTION-LINK-1)" and
 
 When we link to content with a specific tool selected, we want to make sure that someone knows that they will be looking at content relevant to a specific tool even if they do not view the tool switcher tabs in the article.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, see the TOOLNAME documentation in "[ARTICLE TITLE](/PATH/TO/ARTICLE?tool=TOOLNAME)."
 ```
 
@@ -487,7 +487,7 @@ For more information, see the TOOLNAME documentation in "[ARTICLE TITLE](/PATH/T
 
 Use this format to link to a learning path.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 For more information, follow the "[LEARNING PATH TITLE](/)" learning path.
 ```
 
@@ -587,7 +587,7 @@ steps:
 
 For {% data variables.product.prodname_docs %} purposes, a first-party action is any action that has the `actions/`, `github/` or `octo-org/` prefix. For example, this is a first-party action:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 steps:
   - uses: actions/checkout@main
 ```
@@ -596,7 +596,7 @@ steps:
 
 Code examples that use third-party actions must include the following disclaimer as part of the code block:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 # This workflow uses actions that are not certified by {% data variables.product.company_short %}.
 # They are provided by a third-party and are governed by
 # separate terms of service, privacy policy, and support
@@ -605,20 +605,20 @@ Code examples that use third-party actions must include the following disclaimer
 
 To insert this disclaimer, use the `{% raw %}{% data reusables.actions.actions-not-certified-by-github-comment %}{% endnote %}` reusable. If the code block is indented, you must use `indented_data_reference` along with the reusable. For example:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {% raw %}{% indented_data_reference reusables.actions.actions-not-certified-by-github-comment spaces=4 %}{% endraw %}
 ```
 
 For {% data variables.product.prodname_docs %} purposes, a third-party action is any action that doesn't have the `actions/`, `github/` or `octo-org/` prefix. For example, this is a first-party action:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 steps:
   - uses: actions/checkout@main
 ```
 
 This is an example of a third-party action:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 steps:
     - uses: google-github-actions/setup-gcloud@1bee7de035d65ec5da40a31f8589e240eba8fde5
 ```
@@ -630,14 +630,14 @@ Examples:
 
 Code examples that use third-party actions must always pin to a full length commit SHA, instead of the version number or branch:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 steps:
     - uses: google-github-actions/setup-gcloud@1bee7de035d65ec5da40a31f8589e240eba8fde5
 ```
 
 For {% data variables.product.prodname_docs %} purposes, a third-party action is any action that doesn't have one of the following prefixes: `actions/`, `github/`, and `octo-org/`. For example, this is a first-party action:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 steps:
   - uses: actions/javascript-action@main
 ```
@@ -908,7 +908,7 @@ Sectional TOCs must be introduced with a sentence or paragraph that helps people
 
 ### Example of sectional TOCs
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 ## Setting up the application
 
 Set up your application according to your operating system.

content/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax.md

@@ -16,7 +16,7 @@ shortTitle: Basic formatting syntax
 
 To create a heading, add one to six <kbd>#</kbd> symbols before your heading text. The number of <kbd>#</kbd> you use will determine the hierarchy level and typeface size of the heading.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 # A first-level heading
 ## A second-level heading
 ### A third-level heading
@@ -355,7 +355,7 @@ We recommend restricting the use of alerts to one or two per article to avoid ov
 
 Three types of alert are available. You can add an alert with a special blockquote line that specifies the alert type, and then add the alert information in a standard blockquote immediately after.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 > [!NOTE]
 > Highlights information that users should take into account, even when skimming.
 

content/issues/managing-your-tasks-with-tasklists/using-projects-and-tasklists.md

@@ -25,7 +25,7 @@ The "tracks" field shows the number of the issues and pull requests included eac
 
 The "tracked by" field shows the issues with tasklists currently tracking your project's issues. The "tracked by" field can also be used to group and filter views. You can use the filter below to only show issues that are tracked by issue you have specified:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>"
 ```
 
@@ -35,7 +35,7 @@ You can also group a table layout by the "tracked-by" field. This view configura
 
 You can also combine filters and grouping by filtering your project for just the issues you want to use, and then grouping with the "tracked-by" field. The example below shows how to filter a view by multiple issues:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 tracked-by:"<OWNER>/<REPO>#<ISSUE NUMBER>","<OWNER>/<REPO>#<ISSUE NUMBER>"
 ```
 

content/migrations/using-github-enterprise-importer/migrating-repositories-with-github-enterprise-importer/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md

@@ -176,7 +176,7 @@ gh bbs2gh migrate-repo --bbs-server-url BBS-SERVER-URL \
 
 Your migration archive will be generated, and its path will be printed in the command output:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 [12:14] [INFO] Export completed. Your migration archive should be ready on your
 instance at $BITBUCKET_SHARED_HOME/data/migration/export/Bitbucket_export_9.tar
 ```

data/reusables/audit_log/create-s3-policy.md

@@ -1,6 +1,6 @@
 1. In AWS, create a policy that allows {% data variables.product.company_short %} to write to the bucket by copying the following JSON and replacing `EXAMPLE-BUCKET` with the name of your bucket. {% data variables.product.prodname_dotcom %} requires only the permissions in this JSON.
 
-   ```
+   ``` <!-- markdownlint-disable-line fenced-code-language -->
    {
       "Version": "2012-10-17",
       "Statement": [

data/reusables/enterprise-migration-tool/set-up-aws-bucket.md

@@ -2,7 +2,7 @@ In AWS, set up a S3 bucket. For more information, see [Creating a bucket](https:
 
 You will also need an AWS access key and secret key with the following permissions:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 {
     "Version": "2012-10-17",
     "Statement": [

data/reusables/release-notes/2022-09-hotpatch-issue.md

@@ -1,6 +1,6 @@
 Hotpatch upgrades to GitHub Enterprise Server {% ifversion ghes = 3.6 %}3.6.2{% endif %} may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, workaround this issue by connecting to the administrative shell (ssh) and running the following non-interactive command:
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 echo "grub-pc grub-pc/install_devices_empty boolean true" | sudo debconf-set-selections
 ```
 

data/reusables/release-notes/ghe-cluster-config-apply-error.md

@@ -1,6 +1,6 @@
 During an upgrade to GitHub Enterprise Server 3.8.0 on a cluster, after you upgrade nodes other than the primary MySQL node and before you upgrade the primary MySQL node, the following error may appear multiple times after you run `ghe-config-apply`.
 
-```
+``` <!-- markdownlint-disable-line fenced-code-language -->
 Error response from daemon: conflict: unable to delete IMAGE_ID (cannot be forced) - image is being used by running container CONTAINER_ID
 ```