@@ -75,14 +75,18 @@ You can use the `git config` command to change the email address you associate w
 
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. {% data reusables.user-settings.set_your_email_address_in_git %}
+
    ```shell
    git config --global user.email "YOUR_EMAIL"
    ```
+
 3. {% data reusables.user-settings.confirm_git_email_address_correct %}
+
    ```shell
    $ git config --global user.email
    <span class="output">email@example.com</span>
    ```
+
 4. {% data reusables.user-settings.link_email_with_your_account %}
 
 ### Setting your email address for a single repository
@@ -94,12 +98,16 @@ You can change the email address associated with commits you make in a single re
 {% data reusables.command_line.open_the_multi_os_terminal %}
 2. Change the current working directory to the local repository where you want to configure the email address that you associate with your Git commits.
 3. {% data reusables.user-settings.set_your_email_address_in_git %}
+
    ```shell
    git config user.email "YOUR_EMAIL"
    ```
+
 4. {% data reusables.user-settings.confirm_git_email_address_correct %}
+
    ```shell
    $ git config user.email
    <span class="output">email@example.com</span>
    ```
+
 5. {% data reusables.user-settings.link_email_with_your_account %}
@@ -51,6 +51,7 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can
      ```shell copy
      git credential-osxkeychain erase https://github.com
      ```
+
    {% data reusables.git.clear-stored-gcm-credentials %}
 {% data reusables.git.cache-on-repository-path %}
 {% data reusables.accounts.create-personal-access-tokens %}
@@ -70,6 +71,7 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can
      ```shell copy
      cmdkey /delete:LegacyGeneric:target=git:https://github.com
      ```
+
 {% data reusables.git.cache-on-repository-path %}
 {% data reusables.accounts.create-personal-access-tokens %}
 {% data reusables.git.provide-credentials %}
 
@@ -141,6 +141,7 @@ You can use the `cache-dependency-path` parameter for cases when multiple depend
           go-version: '1.17'
           cache-dependency-path: subdir/go.sum
 ```
+
 {% else %}
 
 When caching is enabled, the `setup-go` action searches for the dependency file, `go.sum`, in the repository root and uses the hash of the dependency file as a part of the cache key.
@@ -162,6 +163,7 @@ Alternatively, you can use the `cache-dependency-path` parameter for cases when
           cache: true
           cache-dependency-path: subdir/go.sum
 ```
+
 {% endif %}
 
 If you have a custom requirement or need finer controls for caching, you can use the [`cache` action](https://github.com/marketplace/actions/cache). For more information, see "[AUTOTITLE](/actions/using-workflows/caching-dependencies-to-speed-up-workflows)."
 
@@ -73,6 +73,7 @@ jobs:
   ![Screenshot of a workflow run failure for a Pester test. Test reports "Expected $true, but got $false" and "Error: Process completed with exit code 1."](/assets/images/help/repository/actions-failed-pester-test-updated.png)
 
 - `Invoke-Pester Unit.Tests.ps1 -Passthru` - Uses Pester to execute tests defined in a file called `Unit.Tests.ps1`. For example, to perform the same test described above, the `Unit.Tests.ps1` will contain the following:
+
   ```
   Describe "Check results file is present" {
       It "Check results file is present" {
 
@@ -89,11 +89,13 @@ Alternatively, you can check a `.ruby-version` file  into the root of your repos
 You can add a matrix strategy to run your workflow with more than one version of Ruby. For example, you can test your code against the latest patch releases of versions 3.1, 3.0, and 2.7.
 
 {% raw %}
+
 ```yaml
 strategy:
   matrix:
     ruby-version: ['3.1', '3.0', '2.7']
 ```
+
 {% endraw %}
 
 Each version of Ruby specified in the `ruby-version` array creates a job that runs the same steps. The {% raw %}`${{ matrix.ruby-version }}`{% endraw %} context is used to access the current job's version. For more information about matrix strategies and contexts, see "[AUTOTITLE](/actions/using-workflows/workflow-syntax-for-github-actions)" and "[AUTOTITLE](/actions/learn-github-actions/contexts)."
@@ -156,12 +158,14 @@ The `setup-ruby` actions provides a method to automatically handle the caching o
 To enable caching, set the following.
 
 {% raw %}
+
 ```yaml
 steps:
 - uses: ruby/setup-ruby@ec02537da5712d66d4d50a0f33b7eb52773b5ed1
     with:
       bundler-cache: true
 ```
+
 {% endraw %}
 
 This will configure bundler to install your gems to `vendor/cache`. For each successful run of your workflow, this folder will be cached by {% data variables.product.prodname_actions %} and re-downloaded for subsequent workflow runs. A hash of your gemfile.lock and the Ruby version are used as the cache key. If you install any new gems, or change a version, the cache will be invalidated and bundler will do a fresh install.
 
@@ -101,6 +101,7 @@ jobs:
 You can configure your job to use a single specific version of Swift, such as `5.3.3`.
 
 {% raw %}
+
 ```yaml copy
 steps:
   - uses: swift-actions/setup-swift@65540b95f51493d65f5e59e97dcef9629ddf11bf
@@ -109,6 +110,7 @@ steps:
   - name: Get swift version
     run: swift --version # Swift 5.3.3
 ```
+
 {% endraw %}
 
 ## Building and testing your code
 
@@ -51,6 +51,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
    ```
 
 1. From your terminal, check in your `goodbye.sh` file.
+
    ```shell copy
    git add goodbye.sh
    git commit -m "Add goodbye script"
@@ -63,6 +64,7 @@ Before you begin, you'll create a repository on {% ifversion ghae %}{% data vari
 
     {% raw %}
     **action.yml**
+
     ```yaml copy
     name: 'Hello World'
     description: 'Greet someone'
@@ -121,6 +123,7 @@ The following workflow code uses the completed hello world action that you made
 Copy the workflow code into a `.github/workflows/main.yml` file in another repository, but replace `actions/hello-world-composite-action@v1` with the repository and tag you created. You can also replace the `who-to-greet` input with your name.
 
 **.github/workflows/main.yml**
+
 ```yaml copy
 on: [push]
 
 
@@ -58,6 +58,7 @@ Before you begin, you'll need to create a {% data variables.product.prodname_dot
 In your new `hello-world-docker-action` directory, create a new `Dockerfile` file. Make sure that your filename is capitalized correctly (use a capital `D` but not a capital `f`) if you're having issues. For more information, see "[AUTOTITLE](/actions/creating-actions/dockerfile-support-for-github-actions)."
 
 **Dockerfile**
+
 ```Dockerfile copy
 # Container image that runs your code
 FROM alpine:3.10
@@ -75,6 +76,7 @@ Create a new `action.yml` file in the `hello-world-docker-action` directory you
 
 {% raw %}
 **action.yml**
+
 ```yaml copy
 # action.yml
 name: 'Hello World'
@@ -93,6 +95,7 @@ runs:
   args:
     - ${{ inputs.who-to-greet }}
 ```
+
 {% endraw %}
 
 This metadata defines one `who-to-greet`  input and one `time` output parameter. To pass inputs to the Docker container, you should declare the input using `inputs` and pass the input in the `args` keyword. Everything you include in `args` is passed to the container, but for better discoverability for users of your action, we recommended using inputs.
@@ -110,6 +113,7 @@ Next, the script gets the current time and sets it as an output variable that ac
 1. Add the following code to your `entrypoint.sh` file.
 
    **entrypoint.sh**
+
    ```shell copy
    #!/bin/sh -l
 
@@ -120,6 +124,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 %}
+
    ```
    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)."
 
@@ -153,6 +158,7 @@ In your `hello-world-docker-action` directory, create a `README.md` file that sp
 - An example of how to use your action in a workflow.
 
 **README.md**
+
 ```markdown copy
 # Hello world docker action
 
@@ -205,6 +211,7 @@ Now you're ready to test your action out in a workflow.
 The following workflow code uses the completed _hello world_ action in the public [`actions/hello-world-docker-action`](https://github.com/actions/hello-world-docker-action) repository. Copy the following workflow example code into a `.github/workflows/main.yml` file, but replace the `actions/hello-world-docker-action` with your repository and action name. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}Public actions can be used even if they're not published to {% data variables.product.prodname_marketplace %}. For more information, see "[AUTOTITLE](/actions/creating-actions/publishing-actions-in-github-marketplace#publishing-an-action)." {% endif %}
 
 **.github/workflows/main.yml**
+
 ```yaml copy
 on: [push]
 
@@ -228,6 +235,7 @@ jobs:
 Copy the following example workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name. {% ifversion fpt or ghec %}This private action can't be published to {% data variables.product.prodname_marketplace %}, and can only be used in this repository.{% endif %}
 
 **.github/workflows/main.yml**
+
 ```yaml copy
 on: [push]
 
 
@@ -105,6 +105,7 @@ GitHub Actions provide context information about the webhook event, Git refs, wo
 Add a new file called `index.js`, with the following code.
 
 {% raw %}
+
 ```javascript copy
 const core = require('@actions/core');
 const github = require('@actions/github');
@@ -122,6 +123,7 @@ try {
   core.setFailed(error.message);
 }
 ```
+
 {% endraw %}
 
 If an error is thrown in the above `index.js` example, `core.setFailed(error.message);` uses the actions toolkit [`@actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) package to log a message and set a failing exit code. For more information, see "[AUTOTITLE](/actions/creating-actions/setting-exit-codes-for-actions)."
@@ -224,6 +226,7 @@ This example demonstrates how your new public action can be run from within an e
 Copy the following YAML into a new file at `.github/workflows/main.yml`, and update the `uses: octocat/hello-world-javascript-action@v1.1` line with your username and the name of the public repository you created above. You can also replace the `who-to-greet` input with your name.
 
 {% raw %}
+
 ```yaml copy
 on: [push]
 
@@ -241,6 +244,7 @@ jobs:
       - name: Get the output time
         run: echo "The time was ${{ steps.hello.outputs.time }}"
 ```
+
 {% endraw %}
 
 When this workflow is triggered, the runner will download the `hello-world-javascript-action` action from your public repository and then execute it.
@@ -250,6 +254,7 @@ When this workflow is triggered, the runner will download the `hello-world-javas
 Copy the workflow code into a `.github/workflows/main.yml` file in your action's repository. You can also replace the `who-to-greet` input with your name.
 
 **.github/workflows/main.yml**
+
 ```yaml copy
 on: [push]
 
 
@@ -36,6 +36,7 @@ The following script demonstrates how you can get a user-specified version as in
 {% data variables.product.prodname_dotcom %} provides [`actions/toolkit`](https://github.com/actions/toolkit), which is a set of packages that helps you create actions. This example uses the [`actions/core`](https://github.com/actions/toolkit/tree/main/packages/core) and [`actions/tool-cache`](https://github.com/actions/toolkit/tree/main/packages/tool-cache) packages.
 
 {% raw %}
+
 ```javascript copy
 const core = require('@actions/core');
 const tc = require('@actions/tool-cache');
@@ -56,6 +57,7 @@ async function setup() {
 
 module.exports = setup
 ```
+
 {% endraw %}
 
 To use this script, replace `getDownloadURL` with a function that downloads your CLI. You will also need to create an actions metadata file (`action.yml`) that accepts a `version` input and that runs this script. For full details about how to create an action, see "[AUTOTITLE](/actions/creating-actions/creating-a-javascript-action)."