Removed duplicate actions reusable folder

Author: sophietheking

content/actions/automating-builds-and-tests/building-and-testing-java-with-ant.md

@@ -78,9 +78,9 @@ This workflow performs the following steps:
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Building and testing your code
 

content/actions/automating-builds-and-tests/building-and-testing-java-with-gradle.md

@@ -83,9 +83,9 @@ This workflow performs the following steps:
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Building and testing your code
 

content/actions/automating-builds-and-tests/building-and-testing-java-with-maven.md

@@ -78,9 +78,9 @@ This workflow performs the following steps:
 
 The default starter workflows are excellent starting points when creating your build and test workflow, and you can customize the starter workflow to suit your project’s needs.
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
-{% data reusables.github-actions.java-jvm-architecture %}
+{% data reusables.actions.java-jvm-architecture %}
 
 ## Building and testing your code
 

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

@@ -73,7 +73,7 @@ jobs:
 ```
 {% endraw %}
 
-{% data reusables.github-actions.example-github-runner %}
+{% data reusables.actions.example-github-runner %}
 
 ## Specifying the Node.js version
 
@@ -204,7 +204,7 @@ steps:
 
 ### Example using a private registry and creating the .npmrc file
 
-{% data reusables.github-actions.setup-node-intro %}
+{% data reusables.actions.setup-node-intro %}
 
 To authenticate to your private registry, you'll need to store your npm authentication token as a secret. For example, create a repository secret called `NPM_TOKEN`. For more information, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
 

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

@@ -31,7 +31,7 @@ For a full list of available Xamarin SDK versions on the {% data variables.produ
 * [macOS 10.15](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-10.15-Readme.md#xamarin-bundles)
 * [macOS 11](https://github.com/actions/virtual-environments/blob/main/images/macos/macos-11-Readme.md#xamarin-bundles)
 
-{% data reusables.github-actions.macos-runner-preview %}
+{% data reusables.actions.macos-runner-preview %}
 
 ## Prerequisites
 

content/actions/creating-actions/about-custom-actions.md

@@ -47,13 +47,13 @@ Docker containers package the environment with the {% data variables.product.pro
 
 A Docker container allows you to use specific versions of an operating system, dependencies, tools, and code. For actions that must run in a specific environment configuration, Docker is an ideal option because you can customize the operating system and tools. Because of the latency to build and retrieve the container, Docker container actions are slower than JavaScript actions.
 
-Docker container actions can only execute on runners with a Linux operating system. {% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+Docker container actions can only execute on runners with a Linux operating system. {% data reusables.actions.self-hosted-runner-reqs-docker %}
 
 ### JavaScript actions
 
 JavaScript actions can run directly on a runner machine, and separate the action code from the environment used to run the code. Using a JavaScript action simplifies the action code and executes faster than a Docker container action.
 
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
 
 If you're developing a Node.js project, the {% data variables.product.prodname_actions %} Toolkit provides packages that you can use in your project to speed up development. For more information, see the [actions/toolkit](https://github.com/actions/toolkit) repository.
 

content/actions/creating-actions/creating-a-composite-action.md

@@ -23,7 +23,7 @@ In this guide, you'll learn about the basic components needed to create and use
 
 Once you complete this project, you should understand how to build your own composite action and test it in a workflow.
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerequisites
 

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

@@ -27,9 +27,9 @@ In this guide, you'll learn about the basic components needed to create and use
 
 Once you complete this project, you should understand how to build your own Docker container action and test it in a workflow.
 
-{% data reusables.github-actions.self-hosted-runner-reqs-docker %}
+{% data reusables.actions.self-hosted-runner-reqs-docker %}
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerequisites
 

content/actions/creating-actions/creating-a-javascript-action.md

@@ -29,9 +29,9 @@ This guide uses the {% data variables.product.prodname_actions %} Toolkit Node.j
 
 Once you complete this project, you should understand how to build your own JavaScript action and test it in a workflow.
 
-{% data reusables.github-actions.pure-javascript %}
+{% data reusables.actions.pure-javascript %}
 
-{% data reusables.github-actions.context-injection-warning %}
+{% data reusables.actions.context-injection-warning %}
 
 ## Prerequisites
 

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

@@ -105,7 +105,7 @@ If you define `args` in the action's metadata file, `args` will override the `CM
 
 If you use `CMD` in your `Dockerfile`, follow these guidelines:
 
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
 
 ## Supported Linux capabilities
 

content/actions/creating-actions/metadata-syntax-for-github-actions.md

@@ -272,7 +272,7 @@ For more information, see "[`github context`](/actions/reference/context-and-exp
 
 **Optional** You can use the `if` conditional to prevent a step from running unless a condition is met. You can use any supported context and expression to create a conditional.
 
-{% data reusables.github-actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.expression-syntax-if %} For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 **Example: Using contexts**
 
@@ -441,7 +441,7 @@ runs:
 
 The `args` are used in place of the `CMD` instruction in a `Dockerfile`. If you use `CMD` in your `Dockerfile`, use the guidelines ordered by preference:
 
-{% data reusables.github-actions.dockerfile-guidelines %}
+{% data reusables.actions.dockerfile-guidelines %}
 
 If you need to pass environment variables into an action, make sure your action runs a command shell to perform variable substitution. For example, if your `entrypoint` attribute is set to `"sh -c"`, `args` will be run in a command shell. Alternatively, if your `Dockerfile` uses an `ENTRYPOINT` to run the same command (`"sh -c"`), `args` will execute in a command shell.
 

content/actions/deployment/targeting-different-environments/using-environments-for-deployment.md

@@ -69,13 +69,13 @@ Secrets stored in an environment are only available to workflow jobs that refere
 
 ## Creating an environment
 
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
-{% data reusables.github-actions.new-environment %}
-{% data reusables.github-actions.name-environment %}
+{% data reusables.actions.sidebar-environment %}
+{% data reusables.actions.new-environment %}
+{% data reusables.actions.name-environment %}
 1. Optionally, specify people or teams that must approve workflow jobs that use this environment.
    1. Select **Required reviewers**.
    1. Enter up to 6 people or teams. Only one of the required reviewers needs to approve the job for it to proceed.
@@ -107,13 +107,13 @@ When a workflow references an environment, the environment will appear in the re
 
 ## Deleting an environment
 
-{% data reusables.github-actions.permissions-statement-environment %}
+{% data reusables.actions.permissions-statement-environment %}
 
 Deleting an environment will delete all secrets and protection rules associated with the environment. Any jobs currently waiting because of protection rules from the deleted environment will automatically fail.
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.sidebar-environment %}
+{% data reusables.actions.sidebar-environment %}
 1. Next to the environment that you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
 2. Click **I understand, delete this environment**.
 

content/actions/hosting-your-own-runners/about-self-hosted-runners.md

@@ -18,16 +18,16 @@ type: overview
 
 ## About self-hosted runners
 
-{% data reusables.github-actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
+{% data reusables.actions.self-hosted-runner-description %} Self-hosted runners can be physical, virtual, in a container, on-premises, or in a cloud.
 
 You can add self-hosted runners at various levels in the management hierarchy:
 - Repository-level runners are dedicated to a single repository.
 - Organization-level runners can process jobs for multiple repositories in an organization.
 - Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
 
-Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.github-actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
+Your runner machine connects to {% data variables.product.product_name %} using the {% data variables.product.prodname_actions %} self-hosted runner application. {% data reusables.actions.runner-app-open-source %} When a new version is released, the runner application automatically updates itself when a job is assigned to the runner, or within a week of release if the runner hasn't been assigned any jobs.
 
-{% data reusables.github-actions.self-hosted-runner-auto-removal %}
+{% data reusables.actions.self-hosted-runner-auto-removal %}
 
 For more information about installing and using self-hosted runners, see "[Adding self-hosted runners](/github/automating-your-workflow-with-github-actions/adding-self-hosted-runners)" and "[Using self-hosted runners in a workflow](/github/automating-your-workflow-with-github-actions/using-self-hosted-runners-in-a-workflow)."
 
@@ -70,15 +70,15 @@ You can automatically increase or decrease the number of self-hosted runners in
 
 There are some limits on {% data variables.product.prodname_actions %} usage when using self-hosted runners. These limits are subject to change.
 
-{% data reusables.github-actions.usage-workflow-run-time %}
+{% data reusables.actions.usage-workflow-run-time %}
 - **Job queue time** - Each job for self-hosted runners can be queued for a maximum of 24 hours. If a self-hosted runner does not start executing the job within this limit, the job is terminated and fails to complete.
-{% data reusables.github-actions.usage-api-requests %}
-- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
-{% data reusables.github-actions.usage-workflow-queue-limits %}
+{% data reusables.actions.usage-api-requests %}
+- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
+{% data reusables.actions.usage-workflow-queue-limits %}
 
 ## Workflow continuity for self-hosted runners
 
-{% data reusables.github-actions.runner-workflow-continuity %}
+{% data reusables.actions.runner-workflow-continuity %}
 
 ## Supported architectures and operating systems for self-hosted runners
 
@@ -224,7 +224,7 @@ codeload.github.com
 
 {% ifversion fpt or ghec %}
 
-{% data reusables.github-actions.self-hosted-runner-security %}
+{% data reusables.actions.self-hosted-runner-security %}
 
 {% endif %}
 

content/actions/hosting-your-own-runners/adding-self-hosted-runners.md

@@ -26,7 +26,7 @@ For information on supported operating systems for self-hosted runners, or using
 {% ifversion not ghae %}
 {% warning %}
 
-**Warning:** {% data reusables.github-actions.self-hosted-runner-security %}
+**Warning:** {% data reusables.actions.self-hosted-runner-security %}
 
 For more information, see "[About self-hosted runners](/github/automating-your-workflow-with-github-actions/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
 
@@ -40,18 +40,18 @@ You can add self-hosted runners to a single repository. To add a self-hosted run
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
 1. Click **New self-hosted runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
 1. Under {% ifversion ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, click **Add runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
 ## Adding a self-hosted runner to an organization
 
@@ -60,21 +60,21 @@ You can add self-hosted runners at the organization level, where they can be use
 {% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions %}
-{% data reusables.github-actions.settings-sidebar-actions-runners-updated %}
+{% data reusables.actions.settings-sidebar-actions %}
+{% data reusables.actions.settings-sidebar-actions-runners-updated %}
 1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 {% data reusables.organizations.navigate-to-org %}
 {% data reusables.organizations.org_settings %}
-{% data reusables.github-actions.settings-sidebar-actions-runners %}
+{% data reusables.actions.settings-sidebar-actions-runners %}
 1. Under {% ifversion ghes > 3.1 or ghae %}"Runners", click **Add new**, then click **New runner**.{% elsif ghes < 3.2 %}"Self-hosted runners", click **Add runner**."{% endif %}
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
 
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
 
 ## Adding a self-hosted runner to an enterprise
 
@@ -92,19 +92,19 @@ To add a self-hosted runner to an enterprise account, you must be an enterprise
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% elsif ghae or ghes < 3.4 %}
 To add a self-hosted runner at the enterprise level of {% data variables.product.product_location %}, you must be a site administrator.
 {% data reusables.enterprise-accounts.access-enterprise %}
 {% data reusables.enterprise-accounts.policies-tab %}
 {% data reusables.enterprise-accounts.actions-tab %}
 {% data reusables.enterprise-accounts.actions-runners-tab %}
 1. Click **Add new**, then click **New runner**.
-{% data reusables.github-actions.self-hosted-runner-configure %}
+{% data reusables.actions.self-hosted-runner-configure %}
 {% endif %}
-{% data reusables.github-actions.self-hosted-runner-check-installation-success %}
+{% data reusables.actions.self-hosted-runner-check-installation-success %}
 
-{% data reusables.github-actions.self-hosted-runner-public-repo-access %}
+{% data reusables.actions.self-hosted-runner-public-repo-access %}
 
 ### Making enterprise runners available to repositories