Repo sync

content/actions/automating-builds-and-tests/building-and-testing-nodejs.md

@@ -238,7 +238,7 @@ steps:
 
 The example above creates an _.npmrc_ file with the following contents:
 
-```ini
+```shell
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
 @octocat:registry=https://registry.npmjs.org/
 always-auth=true

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

@@ -42,7 +42,7 @@ In your new `hello-world-docker-action` directory, create a new `Dockerfile` fil
 
 **Dockerfile**
 
-```Dockerfile copy
+```dockerfile copy
 # Container image that runs your code
 FROM alpine:3.10
 

content/actions/creating-actions/dockerfile-support-for-github-actions.md

@@ -79,7 +79,7 @@ ENTRYPOINT ["/entrypoint.sh"]
 
 Using the example Dockerfile above, {% data variables.product.product_name %} will send the `args` configured in the action's metadata file as arguments to `entrypoint.sh`. Add the `#!/bin/sh` [shebang](https://en.wikipedia.org/wiki/Shebang_(Unix)) at the top of the `entrypoint.sh` file to explicitly use the system's [POSIX](https://en.wikipedia.org/wiki/POSIX)-compliant shell.
 
-``` sh
+```shell
 #!/bin/sh
 
 # `$#` expands to the number of arguments and `$@` expands to the supplied `args`
@@ -90,13 +90,13 @@ printf '\n'
 
 Your code must be executable. Make sure the `entrypoint.sh` file has `execute` permissions before using it in a workflow. You can modify the permission from your terminal using this command:
 
-``` sh
+```shell
 chmod +x entrypoint.sh
 ```
 
 When an `ENTRYPOINT` shell script is not executable, you'll receive an error similar to this:
 
-``` sh
+```shell
 Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "exec: \"/entrypoint.sh\": permission denied": unknown
 ```
 

content/actions/deployment/deploying-to-your-cloud-provider/deploying-to-amazon-elastic-container-service.md

@@ -43,12 +43,16 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
    For example, using [the AWS CLI](https://aws.amazon.com/cli/):
 
-   {% raw %}```bash copy
+   {% raw %}
+
+   ```bash copy
    aws ecr create-repository \
        --repository-name MY_ECR_REPOSITORY \
        --region MY_AWS_REGION
 
-   ```{% endraw %}
+   ```
+
+   {% endraw %}
 
    Ensure that you use the same Amazon ECR repository name (represented here by `MY_ECR_REPOSITORY`) for the `ECR_REPOSITORY` variable in the workflow below.
 
@@ -64,10 +68,15 @@ Before creating your {% data variables.product.prodname_actions %} workflow, you
 
    The format of the file should be the same as the output generated by:
 
-   {% raw %}```bash copy
+   {% raw %}
+
+   ```bash copy
+
    aws ecs register-task-definition --generate-cli-skeleton
 
-   ```{% endraw %}
+   ```
+
+   {% endraw %}
 
    Ensure that you set the `ECS_TASK_DEFINITION` variable in the workflow below as the path to the JSON file.
 

content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services.md

@@ -65,7 +65,7 @@ Edit the trust policy, adding the `sub` field to the validation conditions. For
 
 If you use a workflow with an environment, the `sub` field must reference the environment name: `repo:OWNER/REPOSITORY:environment:NAME`. For more information, see "[AUTOTITLE](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#understanding-the-oidc-token)."
 
-```json{:copy}
+```json copy
 "Condition": {
   "StringEquals": {
     "{% ifversion ghes %}HOSTNAME/_services/token{% else %}token.actions.githubusercontent.com{% endif %}:aud": "sts.amazonaws.com",

content/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-pypi.md

@@ -51,7 +51,7 @@ The [`pypa/gh-action-pypi-publish`](https://github.com/marketplace/actions/pypi-
 
 The following example uses the `pypa/gh-action-pypi-publish` action to exchange an OIDC token for a PyPI API token, which is then used to upload a package's release distributions to PyPI.
 
-```yaml{:copy}
+```yaml copy
 jobs:
   release-build:
     runs-on: ubuntu-latest

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

@@ -113,7 +113,7 @@ You can create your own runner image that meets your requirements. Your runner i
 
 You can use the following example Dockerfile to start creating your own runner image.
 
-```Dockerfile copy
+```dockerfile copy
 FROM mcr.microsoft.com/dotnet/runtime-deps:6.0 as build
 
 # Replace value with the latest runner release version

content/actions/hosting-your-own-runners/managing-self-hosted-runners/using-a-proxy-server-with-self-hosted-runners.md

@@ -45,7 +45,7 @@ If setting environment variables is not practical, you can set the proxy configu
 
 ### Example `.env` proxy configuration
 
-```ini
+```shell
 https_proxy=http://proxy.local:8080
 no_proxy=example.com,myserver.local:443
 ```

content/actions/learn-github-actions/expressions.md

@@ -196,7 +196,7 @@ Replaces values in the `string`, with the variable `replaceValueN`. Variables in
 
 {% raw %}
 
-```js
+```javascript
 format('Hello {0} {1} {2}', 'Mona', 'the', 'Octocat')
 ```
 
@@ -208,7 +208,7 @@ Returns 'Hello Mona the Octocat'.
 
 {% raw %}
 
-```js
+```javascript
 format('{{Hello {0} {1} {2}!}}', 'Mona', 'the', 'Octocat')
 ```
 

content/actions/migrating-to-github-actions/automated-migrations/migrating-from-circleci-with-github-actions-importer.md

@@ -300,7 +300,7 @@ gh actions-importer audit circle-ci --output-dir ./output/ --include-from reposi
 
 The file supplied for this parameter must be a a line-delimited list of repositories, for example:
 
-```txt
+```text
 repository_one
 repository_two
 repository_three

content/actions/migrating-to-github-actions/automated-migrations/supplemental-arguments-and-settings.md

@@ -51,7 +51,7 @@ A credentials file must be a YAML file containing a list of server and access to
 
 For example:
 
-```yml
+```yaml
 - url: https://github.com
   access_token: ghp_mygeneraltoken
 - url: https://github.com/specific_org/
@@ -69,7 +69,7 @@ For the above credentials file, {% data variables.product.prodname_actions_impor
 
 For example:
 
-```yml
+```yaml
 - url: https://gitlab.com
   access_token: super_secret_token
   provider: gitlab

content/actions/publishing-packages/publishing-nodejs-packages.md

@@ -83,7 +83,7 @@ jobs:
 
 In the example above, the `setup-node` action creates an `.npmrc` file on the runner with the following contents:
 
-```ini
+```shell
 //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}
 registry=https://registry.npmjs.org/
 always-auth=true
@@ -148,7 +148,7 @@ jobs:
 
 The `setup-node` action creates an `.npmrc` file on the runner. When you use the `scope` input to the `setup-node` action, the `.npmrc` file includes the scope prefix. By default, the `setup-node` action sets the scope in the `.npmrc` file to the account that contains that workflow file.
 
-```ini
+```shell
 //npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}
 @octocat:registry=https://npm.pkg.github.com
 always-auth=true

content/actions/using-containerized-services/creating-postgresql-service-containers.md

@@ -325,7 +325,7 @@ The script creates a table and populates it with placeholder data. To test that
 
 When you run this workflow, you should see the following output in the "Connect to PostgreSQL" step, which confirms that you successfully created the PostgreSQL table and added data:
 
-```json
+```text
 null [ { id: 1,
     firstname: 'Mona the',
     lastname: 'Octocat',

content/actions/using-workflows/workflow-commands-for-github-actions.md

@@ -38,7 +38,7 @@ echo "::workflow-command parameter1={data},parameter2={data}::{command value}"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::workflow-command parameter1={data},parameter2={data}::{command value}"
 ```
 
@@ -179,7 +179,7 @@ echo "::set-output name=action_fruit::strawberry"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::set-output name=action_fruit::strawberry"
 ```
 
@@ -206,7 +206,7 @@ echo "::debug::Set the Octocat variable"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::debug::Set the Octocat variable"
 ```
 
@@ -234,7 +234,7 @@ echo "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::notice file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
@@ -262,7 +262,7 @@ echo "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::warning file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
@@ -290,7 +290,7 @@ echo "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::error file=app.js,line=1,col=5,endColumn=7::Missing semicolon"
 ```
 
@@ -363,7 +363,7 @@ echo "::add-mask::Mona The Octocat"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 Write-Output "::add-mask::Mona The Octocat"
 ```
 
@@ -783,7 +783,7 @@ echo "{environment_variable_name}={value}" >> "$GITHUB_ENV"
 
 - Using PowerShell version 6 and higher:
 
-  ```pwsh copy
+  ```powershell copy
   "{environment_variable_name}={value}" | Out-File -FilePath $env:GITHUB_ENV -Append
   ```
 
@@ -901,7 +901,7 @@ echo "{name}={value}" >> "$GITHUB_OUTPUT"
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 "{name}=value" | Out-File -FilePath $env:GITHUB_OUTPUT -Append
 ```
 
@@ -957,7 +957,7 @@ echo "{markdown content}" >> $GITHUB_STEP_SUMMARY
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 "{markdown content}" | Out-File -FilePath $env:GITHUB_STEP_SUMMARY -Append
 ```
 
@@ -981,7 +981,7 @@ echo "### Hello world! :rocket:" >> $GITHUB_STEP_SUMMARY
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 "### Hello world! :rocket:" | Out-File -FilePath $env:GITHUB_STEP_SUMMARY -Append
 ```
 
@@ -1101,7 +1101,7 @@ echo "{path}" >> $GITHUB_PATH
 
 {% powershell %}
 
-```pwsh copy
+```powershell copy
 "{path}" | Out-File -FilePath $env:GITHUB_PATH -Append
 ```
 
@@ -1123,7 +1123,7 @@ echo "$HOME/.local/bin" >> $GITHUB_PATH
 
 This example demonstrates how to add the user `$env:HOMEPATH/.local/bin` directory to `PATH`:
 
-```pwsh copy
+```powershell copy
 "$env:HOMEPATH/.local/bin" | Out-File -FilePath $env:GITHUB_PATH -Append
 ```
 

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.
 
-```
+```text
 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:
 
-```
+```text
 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]
 ```
 
-```
+```text
 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.
 
-```
+```text
 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.
 
-```
+```shell
 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.
 
-   ```
+   ```shell
    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.
 
-   ```
+   ```shell
    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.
 
-   ```
+   ```shell
    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.
 
-   ```
+   ```shell
    git clone https://github.com/github/backup-utils.git
    ```
 
 1. To change into the cloned repository, run the following command.
 
-   ```
+   ```shell
    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.
 
-   ```
+   ```shell
    cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
    ```