Update all files to use {% data %} (#15253)

* Add back changes from prior to purge

* Manually fix some invalid Liquid

* Updoot render-content

* Improve test messages to show correct output

* Run el scripto

* Pass the remaining test

data/reusables/github-actions/actions-billing.md

@@ -1 +1 @@
-{{ site.data.variables.product.prodname_actions }} usage is free for public repositories and self-hosted runners. For private repositories, each {{ site.data.variables.product.prodname_dotcom }} account receives a certain amount of free minutes and storage, depending on the product used with the account.
+{% data variables.product.prodname_actions %} usage is free for public repositories and self-hosted runners. For private repositories, each {% data variables.product.prodname_dotcom %} account receives a certain amount of free minutes and storage, depending on the product used with the account.

data/reusables/github-actions/actions-do-not-trigger-workflows.md

@@ -1 +1 @@
-When you use the repository's `GITHUB_TOKEN` to perform tasks on behalf of the {{ site.data.variables.product.prodname_actions }} app, events triggered by the `GITHUB_TOKEN` will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's `GITHUB_TOKEN`, a new workflow will not run even when the repository contains a workflow configured to run when `push` events occur.
+When you use the repository's `GITHUB_TOKEN` to perform tasks on behalf of the {% data variables.product.prodname_actions %} app, events triggered by the `GITHUB_TOKEN` will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's `GITHUB_TOKEN`, a new workflow will not run even when the repository contains a workflow configured to run when `push` events occur.

data/reusables/github-actions/actions-spending-limit.md

@@ -1 +1 @@
-By default, your account will have a spending limit of $0, which prevents additional usage of minutes or storage after you reach these limits. If you increase your spending limit above the default of $0, you will be billed for any minutes or storage beyond the limits, also called overages. {{ site.data.variables.product.prodname_dotcom }} charges usage to the account that owns the repository where the workflow is run. Any coupons on your account do not apply to {{ site.data.variables.product.prodname_actions }} overages.
+By default, your account will have a spending limit of $0, which prevents additional usage of minutes or storage after you reach these limits. If you increase your spending limit above the default of $0, you will be billed for any minutes or storage beyond the limits, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where the workflow is run. Any coupons on your account do not apply to {% data variables.product.prodname_actions %} overages.

data/reusables/github-actions/contacting-support.md

@@ -1,8 +1,8 @@
-If you need help with anything related to workflow configuration, such as syntax, {{ site.data.variables.product.prodname_dotcom }}-hosted runners, or building actions, look for an existing topic or start a new one in the [{{ site.data.variables.product.prodname_gcf }}'s {{ site.data.variables.product.prodname_actions }} board](https://github.community/c/github-actions).
+If you need help with anything related to workflow configuration, such as syntax, {% data variables.product.prodname_dotcom %}-hosted runners, or building actions, look for an existing topic or start a new one in the [{% data variables.product.prodname_gcf %}'s {% data variables.product.prodname_actions %} board](https://github.community/c/github-actions).
 
-If you have feedback or feature requests for {{ site.data.variables.product.prodname_actions }}, share those in the {{ site.data.variables.contact.contact_feedback_actions }}.
+If you have feedback or feature requests for {% data variables.product.prodname_actions %}, share those in the {% data variables.contact.contact_feedback_actions %}.
 
-Contact {{ site.data.variables.contact.contact_support }} for any of the following, whether your use or intended use falls into the usage limit categories:
+Contact {% data variables.contact.contact_support %} for any of the following, whether your use or intended use falls into the usage limit categories:
 
 * If you believe your account has been incorrectly restricted
 * If you encounter an unexpected error when executing one of your Actions, for example: a unique ID

data/reusables/github-actions/defaults-override.md

@@ -1 +1 @@
-When more than one default setting is defined with the same name, {{ site.data.variables.product.prodname_dotcom }} uses the most specific default setting. For example, a default setting defined in a job will override a default setting that has the same name defined in a workflow.
+When more than one default setting is defined with the same name, {% data variables.product.prodname_dotcom %} uses the most specific default setting. For example, a default setting defined in a job will override a default setting that has the same name defined in a workflow.

data/reusables/github-actions/disabled-actions-description.md

@@ -1 +1 @@
-When you disable {{ site.data.variables.product.prodname_actions }}, no workflows run in your repository.
+When you disable {% data variables.product.prodname_actions %}, no workflows run in your repository.

data/reusables/github-actions/disabling-github-actions.md

@@ -1 +1 @@
-By default, {% if currentVersion ver_gt "enterprise-server@2.21" %}after {{ site.data.variables.product.prodname_actions }} is enabled on {{ site.data.variables.product.product_location }}, it{% else if if currentVersion == "free-pro-team@latest" %}{{ site.data.variables.product.prodname_actions }}{% endif %} is enabled on all repositories and organizations. You can choose to disable {{ site.data.variables.product.prodname_actions }} or limit them to private actions only, which means that people can only use actions that exist in your repository.
+By default, {% if currentVersion ver_gt "enterprise-server@2.21" %}after {% data variables.product.prodname_actions %} is enabled on {% data variables.product.product_location %}, it{% else if if currentVersion == "free-pro-team@latest" %}{% data variables.product.prodname_actions %}{% endif %} is enabled on all repositories and organizations. You can choose to disable {% data variables.product.prodname_actions %} or limit them to private actions only, which means that people can only use actions that exist in your repository.

data/reusables/github-actions/docker-container-os-support.md

@@ -2,7 +2,7 @@
 
 **Note:** If your workflows use Docker container actions or service containers, then you must use a Linux runner:
 
-* If you are using {{ site.data.variables.product.prodname_dotcom }}-hosted runners, you must use the `ubuntu-latest` runner.
+* If you are using {% data variables.product.prodname_dotcom %}-hosted runners, you must use the `ubuntu-latest` runner.
 * If you are using self-hosted runners, you must use a Linux machine as your runner and Docker must be installed.
 
 {% endnote %}

data/reusables/github-actions/docker-tag-with-ref.md

@@ -1 +1 @@
-The above workflow checks out the {{ site.data.variables.product.prodname_dotcom }} repository, and uses the `build-push-action` action to build and push the Docker image. It sets the `build-push-action` option [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) to automatically tag the built Docker image with the Git reference of the workflow event. This workflow is triggered on publishing a {{ site.data.variables.product.prodname_dotcom }} release, so the reference will be the Git tag for the release.
+The above workflow checks out the {% data variables.product.prodname_dotcom %} repository, and uses the `build-push-action` action to build and push the Docker image. It sets the `build-push-action` option [`tag_with_ref`](https://github.com/marketplace/actions/build-and-push-docker-images#tag_with_ref) to automatically tag the built Docker image with the Git reference of the workflow event. This workflow is triggered on publishing a {% data variables.product.prodname_dotcom %} release, so the reference will be the Git tag for the release.

data/reusables/github-actions/enabled-actions-description.md

@@ -1 +1 @@
-When you enable {{ site.data.variables.product.prodname_actions }}, workflows are able to run actions located within your repository and any other public repository.
+When you enable {% data variables.product.prodname_actions %}, workflows are able to run actions located within your repository and any other public repository.

data/reusables/github-actions/enterprise-billing-details.md

@@ -1 +1 @@
-The usage includes the total minutes used by each organization. The combined summary for {{ site.data.variables.product.prodname_actions }} and {{ site.data.variables.product.prodname_registry }} does not list included minutes, paid minutes, or a price estimate per GB of storage.
+The usage includes the total minutes used by each organization. The combined summary for {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %} does not list included minutes, paid minutes, or a price estimate per GB of storage.

data/reusables/github-actions/example-github-runner.md

@@ -1,6 +1,6 @@
 ### Running on a different operating system
 
-The starter workflow template configures jobs to run on Linux, using the {{ site.data.variables.product.prodname_dotcom }}-hosted `ubuntu-latest` runners. You can change the `runs-on` key to run your jobs on a different operating system. For example, you can use the {{ site.data.variables.product.prodname_dotcom }}-hosted Windows runners.
+The starter workflow template configures jobs to run on Linux, using the {% data variables.product.prodname_dotcom %}-hosted `ubuntu-latest` runners. You can change the `runs-on` key to run your jobs on a different operating system. For example, you can use the {% data variables.product.prodname_dotcom %}-hosted Windows runners.
 
 {% raw %}
 ```yaml
@@ -8,7 +8,7 @@ runs-on: windows-latest
 ```
 {% endraw %}
 
-Or, you can run on the {{ site.data.variables.product.prodname_dotcom }}-hosted macOS runners.
+Or, you can run on the {% data variables.product.prodname_dotcom %}-hosted macOS runners.
 
 {% raw %}
 ```yaml
@@ -16,4 +16,4 @@ runs-on: macos-latest
 ```
 {% endraw %}
 
-You can also run jobs in Docker containers, or you can provide a self-hosted runner that runs on your own infrastructure. For more information, see "[Workflow syntax for {{ site.data.variables.product.prodname_actions }}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."
+You can also run jobs in Docker containers, or you can provide a self-hosted runner that runs on your own infrastructure. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."

data/reusables/github-actions/expression-syntax-if.md

@@ -1 +1 @@
-When you use expressions in an `if` conditional, you may omit the expression syntax ({% raw %}`${{ }}`{% endraw %}) because {{ site.data.variables.product.prodname_dotcom }} automatically evaluates the `if` conditional as an expression.
+When you use expressions in an `if` conditional, you may omit the expression syntax ({% raw %}`${{ }}`{% endraw %}) because {% data variables.product.prodname_dotcom %} automatically evaluates the `if` conditional as an expression.

data/reusables/github-actions/github-actions-minutes-change.md

@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** After May, 14, 2020, {{ site.data.variables.product.prodname_team }} will include 3,000 {{ site.data.variables.product.prodname_actions }} minutes per month.
+**Note:** After May, 14, 2020, {% data variables.product.prodname_team %} will include 3,000 {% data variables.product.prodname_actions %} minutes per month.
 
 {% endnote %}

data/reusables/github-actions/github-context-warning.md

@@ -1,5 +1,5 @@
 {% warning %}
 
-**Warning:** When using the whole `github` context, be mindful that it includes sensitive information such as `github.token`. {{ site.data.variables.product.prodname_dotcom }} masks secrets when they are printed to the console, but you should be cautious when exporting or printing the context.
+**Warning:** When using the whole `github` context, be mindful that it includes sensitive information such as `github.token`. {% data variables.product.prodname_dotcom %} masks secrets when they are printed to the console, but you should be cautious when exporting or printing the context.
 
 {% endwarning %}

data/reusables/github-actions/invalid-workflow-files.md

@@ -1,5 +1,5 @@
 {% note %}
 
-**Note:** Ensure that you only commit valid workflow files to your repository. If `.github/workflows` contains an invalid workflow file, {{ site.data.variables.product.prodname_actions }} generates a failed workflow run for every new commit.
+**Note:** Ensure that you only commit valid workflow files to your repository. If `.github/workflows` contains an invalid workflow file, {% data variables.product.prodname_actions %} generates a failed workflow run for every new commit.
 
 {% endnote %}

data/reusables/github-actions/ip-allow-list-self-hosted-runners.md

@@ -1,7 +1,7 @@
 {% warning %}
 
-**Warning**: If you use an IP allow list and would also like to use {{ site.data.variables.product.prodname_actions }}, you must use self-hosted runners. For more information, see "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
+**Warning**: If you use an IP allow list and would also like to use {% data variables.product.prodname_actions %}, you must use self-hosted runners. For more information, see "[Hosting your own runners](/actions/automating-your-workflow-with-github-actions/about-self-hosted-runners)."
 
 {% endwarning %}
 
-To allow your self-hosted runners to communicate with {{ site.data.variables.product.prodname_dotcom }}, add the IP address or IP address range of your self-hosted runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."
+To allow your self-hosted runners to communicate with {% data variables.product.prodname_dotcom %}, add the IP address or IP address range of your self-hosted runners to the IP allow list. For more information, see "[Adding an allowed IP address](#adding-an-allowed-ip-address)."

data/reusables/github-actions/permissions-statement-secrets-api.md

@@ -1 +1 @@
-To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{{ site.data.variables.product.prodname_actions }} secrets API](/v3/actions/secrets/)."
+To create secrets using the REST API, you must have write access to the repository or admin access to the organization. For more information, see "[{% data variables.product.prodname_actions %} secrets API](/v3/actions/secrets/)."

data/reusables/github-actions/publish-to-packages-workflow-step.md

@@ -1 +1 @@
-Runs the `mvn -B deploy` command to publish to {{ site.data.variables.product.prodname_registry }}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret.
+Runs the `mvn -B deploy` command to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the contents of the `GITHUB_TOKEN` secret.

data/reusables/github-actions/publishing-java-packages-intro.md

@@ -1 +1 @@
-This guide shows you how to create a workflow that publishes Java packages to {{ site.data.variables.product.prodname_registry }} and the Maven Central Repository. With a single workflow, you can publish packages to a single repository or to multiple repositories.
+This guide shows you how to create a workflow that publishes Java packages to {% data variables.product.prodname_registry %} and the Maven Central Repository. With a single workflow, you can publish packages to a single repository or to multiple repositories.

data/reusables/github-actions/release-trigger-workflow.md

@@ -1 +1 @@
-Each time you create a new release on {{ site.data.variables.product.prodname_dotcom }}, you can trigger a workflow to publish your image. The workflow in the example below runs when the `release` event triggers with the `created` activity type. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release).
+Each time you create a new release on {% data variables.product.prodname_dotcom %}, you can trigger a workflow to publish your image. The workflow in the example below runs when the `release` event triggers with the `created` activity type. For more information on the `release` event, see "[Events that trigger workflows](/actions/reference/events-that-trigger-workflows#release).

data/reusables/github-actions/runner-app-open-source.md

@@ -1 +1 @@
-The {{ site.data.variables.product.prodname_actions }} runner application is open source. You can contribute and file issues in the [runner](https://github.com/actions/runner) repository.
+The {% data variables.product.prodname_actions %} runner application is open source. You can contribute and file issues in the [runner](https://github.com/actions/runner) repository.

data/reusables/github-actions/self-hosted-runner-auto-removal.md

@@ -1 +1 @@
-A self-hosted runner is automatically removed from {{ site.data.variables.product.product_name }} if it has not connected to {{ site.data.variables.product.prodname_actions }} for more than 30 days.
+A self-hosted runner is automatically removed from {% data variables.product.product_name %} if it has not connected to {% data variables.product.prodname_actions %} for more than 30 days.

data/reusables/github-actions/self-hosted-runner-check-installation-success.md

@@ -3,8 +3,8 @@
 
 After completing the steps to add a self-hosted runner, the runner and its status are now listed under "Self-hosted runners".
 
-The self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to {{ site.data.variables.product.product_name }} and ready to receive jobs, you will see the following message on machine's terminal.
+The self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to {% data variables.product.product_name %} and ready to receive jobs, you will see the following message on machine's terminal.
 
-{{ site.data.reusables.github-actions.self-hosted-runner-connected-output }}
+{% data reusables.github-actions.self-hosted-runner-connected-output %}
 
 For more information, see "[Monitoring and troubleshooting self-hosted runners](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners)."

data/reusables/github-actions/self-hosted-runner-configure.md

@@ -14,6 +14,6 @@
 
    The instructions walk you through completing these tasks:
    - Downloading and extracting the self-hosted runner application.
-   - Running the `config` script to configure the self-hosted runner application and register it with {{ site.data.variables.product.prodname_actions }}. The `config` script requires the destination URL and an automatically-generated time-limited token to authenticate the request.
+   - Running the `config` script to configure the self-hosted runner application and register it with {% data variables.product.prodname_actions %}. The `config` script requires the destination URL and an automatically-generated time-limited token to authenticate the request.
      - On Windows, the `config` script also asks if you would like to install the self-hosted runner application as a service. For Linux and macOS, you can install a service after you finish adding the runner. For more information, see "[Configuring the self-hosted runner application as a service](/actions/automating-your-workflow-with-github-actions/configuring-the-self-hosted-runner-application-as-a-service)."
-   - Running the self-hosted runner application to connect the machine to {{ site.data.variables.product.prodname_actions }}.
+   - Running the self-hosted runner application to connect the machine to {% data variables.product.prodname_actions %}.

data/reusables/github-actions/self-hosted-runner-description.md

@@ -1 +1 @@
-Self-hosted runners offer more control of hardware, operating system, and software tools than {{ site.data.variables.product.prodname_dotcom }}-hosted runners provide. With self-hosted runners, you can choose to create a custom hardware configuration with more processing power or memory to run larger jobs, install software available on your local network, and choose an operating system not offered by {{ site.data.variables.product.prodname_dotcom }}-hosted runners.
+Self-hosted runners offer more control of hardware, operating system, and software tools than {% data variables.product.prodname_dotcom %}-hosted runners provide. With self-hosted runners, you can choose to create a custom hardware configuration with more processing power or memory to run larger jobs, install software available on your local network, and choose an operating system not offered by {% data variables.product.prodname_dotcom %}-hosted runners.

data/reusables/github-actions/self-hosted-runner-management-permissions-required.md

@@ -1,9 +1,9 @@
-A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {{ site.data.variables.product.prodname_dotcom }}{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {{ site.data.variables.product.product_location }}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
+A self-hosted runner can be located in either your repository, organization, or {% if currentVersion == "free-pro-team@latest" %}enterprise account settings on {% data variables.product.prodname_dotcom %}{% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %} enterprise settings on {% data variables.product.product_location %}{% endif %}. To manage a self-hosted runner, you must have the following permissions, depending on where the self-hosted runner was added:
 - **User repository**: You must be the repository owner.
 - **Organization**: You must be an organization owner. 
 - **Organization repository**: You must be an organization owner, or have admin access to the repository.
 {% if currentVersion == "free-pro-team@latest" %}
 - **Enterprise account**: You must be an enterprise owner.
 {% else if currentVersion != "free-pro-team@latest" and currentVersion ver_gt "enterprise-server@2.21" %}
-- **Enterprise**: You must be a {{ site.data.variables.product.prodname_enterprise }} site administrator.
+- **Enterprise**: You must be a {% data variables.product.prodname_enterprise %} site administrator.
 {% endif %}

data/reusables/github-actions/self-hosted-runner-navigate-to-repo-org-enterprise.md

@@ -5,7 +5,7 @@
      1. In the upper-right corner of any page, click {% octicon "rocket" aria-label="The rocket ship" %}.
      1. In the left sidebar, click **Enterprise overview**. 
      1. {% endif %} In the enterprise sidebar, {% octicon "law" aria-label="The law icon" %} **Policies**.
-1. Navigate to the {{ site.data.variables.product.prodname_actions }} settings:
+1. Navigate to the {% data variables.product.prodname_actions %} settings:
    * **In an organization or repository**: click **Actions** in the left sidebar.
      
      ![Actions setting](/assets/images/help/settings/settings-sidebar-actions.png)

data/reusables/github-actions/self-hosted-runner-removing-a-runner.md

@@ -8,8 +8,8 @@
 
         The removal command does the following tasks:
 
-        * Removes the runner from {{ site.data.variables.product.product_name }}.
+        * Removes the runner from {% data variables.product.product_name %}.
         * Removes any self-hosted runner application configuration files on the machine.
         * Removes any services configured if not running in interactive mode.
 
-    * **If you don't have access to the machine:** Click **Yes, force remove this runner** to force {{ site.data.variables.product.product_name }} to remove the runner.
+    * **If you don't have access to the machine:** Click **Yes, force remove this runner** to force {% data variables.product.product_name %} to remove the runner.

data/reusables/github-actions/self-hosted-runner-reusing.md

@@ -1 +1 @@
-Alternatively, if you don't have access to the repository, organization, or enterprise on {{ site.data.variables.product.product_name }} to remove a runner, but you would like to re-use the runner machine, then you can delete the `.runner` file inside the self-hosted runner application directory. This allows the runner to be registered without having to re-download the self-hosted runner application.
+Alternatively, if you don't have access to the repository, organization, or enterprise on {% data variables.product.product_name %} to remove a runner, but you would like to re-use the runner machine, then you can delete the `.runner` file inside the self-hosted runner application directory. This allows the runner to be registered without having to re-download the self-hosted runner application.

data/reusables/github-actions/service-container-host-runner.md

@@ -1 +1 @@
-The example uses the `ubuntu-latest` {{ site.data.variables.product.prodname_dotcom }}-hosted runner as the Docker host.
+The example uses the `ubuntu-latest` {% data variables.product.prodname_dotcom %}-hosted runner as the Docker host.

data/reusables/github-actions/service-container-host.md

@@ -1 +1 @@
-This workflow configures a job that runs in the `node:10.18-jessie` container and uses the `ubuntu-latest` {{ site.data.variables.product.prodname_dotcom }}-hosted runner as the Docker host for the container. For more information about the `node:10.18-jessie` container, see the [node image](https://hub.docker.com/_/node) on Docker Hub.
+This workflow configures a job that runs in the `node:10.18-jessie` container and uses the `ubuntu-latest` {% data variables.product.prodname_dotcom %}-hosted runner as the Docker host for the container. For more information about the `node:10.18-jessie` container, see the [node image](https://hub.docker.com/_/node) on Docker Hub.

data/reusables/github-actions/service-container-prereqs.md

@@ -1 +1 @@
-You should be familiar with how service containers work with {{ site.data.variables.product.prodname_actions }} and the networking differences between running jobs directly on the runner or in a container. For more information, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."
+You should be familiar with how service containers work with {% data variables.product.prodname_actions %} and the networking differences between running jobs directly on the runner or in a container. For more information, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers)."

data/reusables/github-actions/spending-limit-enterprise-account.md

@@ -1 +1 @@
-If you pay for your enterprise account by invoice, you cannot manage the spending limit for your enterprise account on {{ site.data.variables.product.product_name }}. If you want to allow organizations owned by your enterprise account to use {{ site.data.variables.product.prodname_actions }} beyond the storage or data transfer included in their accounts, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact).
+If you pay for your enterprise account by invoice, you cannot manage the spending limit for your enterprise account on {% data variables.product.product_name %}. If you want to allow organizations owned by your enterprise account to use {% data variables.product.prodname_actions %} beyond the storage or data transfer included in their accounts, you can prepay for overages. Because overages must prepaid, you cannot enable unlimited spending on accounts paid by invoice. Your spending limit will be 150% of the amount you prepaid. If you have any questions, [contact our account management team](https://enterprise.github.com/contact).