jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Removed duplicate actions reusable folder

Browse Source
This commit is contained in:
Sophie
2022-02-25 15:51:14 +01:00
parent 87a7257bf4
commit 50c0b2d0b0
196 changed files with 334 additions and 334 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -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

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

@@ -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

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

@@ -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

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

@@ -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)."

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

@@ -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

4
content/actions/creating-actions/about-custom-actions.md
View File

@@ -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.

2
content/actions/creating-actions/creating-a-composite-action.md
View File

@@ -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

4
content/actions/creating-actions/creating-a-docker-container-action.md
View File

@@ -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

4
content/actions/creating-actions/creating-a-javascript-action.md
View File

@@ -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

2
content/actions/creating-actions/dockerfile-support-for-github-actions.md
View File

@@ -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

4
content/actions/creating-actions/metadata-syntax-for-github-actions.md
View File

@@ -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.

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

@@ -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**.

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

@@ -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 %}

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

@@ -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,7 +92,7 @@ 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 %}
@@ -100,11 +100,11 @@ To add a self-hosted runner at the enterprise level of {% data variables.product
{% 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

22
content/actions/hosting-your-own-runners/managing-access-to-self-hosted-runners-using-groups.md
View File

@@ -48,9 +48,9 @@ When creating a group, you must choose a policy that defines which repositories
{% ifversion 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-runner-groups %}
{% data reusables.actions.settings-sidebar-actions-runner-groups %}
1. In the "Runner groups" section, click **New runner group**.
{% data reusables.github-actions.runner-group-assign-policy-repo %}
{% data reusables.actions.runner-group-assign-policy-repo %}
{% warning %}
@@ -59,11 +59,11 @@ When creating a group, you must choose a policy that defines which repositories
For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
{% data reusables.github-actions.self-hosted-runner-create-group %}
{% data reusables.actions.self-hosted-runner-create-group %}
{% 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"{% elsif ghes < 3.2 %}"Self-hosted runners"{% endif %}, click **Add new**, and then **New group**.
![Add runner group](/assets/images/help/settings/actions-org-add-runner-group.png)
@@ -99,7 +99,7 @@ When creating a group, you must choose a policy that defines which organizations
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.enterprise-accounts.actions-runner-groups-tab %}
1. Click **New runner group**.
{% data reusables.github-actions.runner-group-assign-policy-org %}
{% data reusables.actions.runner-group-assign-policy-org %}
{% warning %}
@@ -110,7 +110,7 @@ When creating a group, you must choose a policy that defines which organizations
For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners#self-hosted-runner-security-with-public-repositories)."
{% endwarning %}
{% data reusables.github-actions.self-hosted-runner-create-group %}
{% data reusables.actions.self-hosted-runner-create-group %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
@@ -142,8 +142,8 @@ When creating a group, you must choose a policy that defines which organizations
You can update the access policy of a runner group, or rename a runner group.
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.settings-sidebar-actions-runner-groups-selection %}
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-groups-selection %}
1. Modify the access options, or change the runner group name.
{% warning %}
@@ -156,7 +156,7 @@ You can update the access policy of a runner group, or rename a runner group.
{% endwarning %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.github-actions.self-hosted-runner-configure-runner-group-access %}
{% data reusables.actions.self-hosted-runner-configure-runner-group-access %}
{% endif %}
{% ifversion ghec or ghes or ghae %}
@@ -178,7 +178,7 @@ Could not find any self-hosted runner group named "rg-runnergroup".
If you don't specify a runner group during the registration process, your new self-hosted runners are automatically assigned to the default group, and can then be moved to another group.
{% data reusables.github-actions.self-hosted-runner-navigate-to-org-enterprise %}
{% data reusables.actions.self-hosted-runner-navigate-to-org-enterprise %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
1. In the "Runners" list, click the runner that you want to configure.
2. Select the Runner group dropdown menu.
@@ -197,7 +197,7 @@ If you don't specify a runner group during the registration process, your new se
Self-hosted runners are automatically returned to the default group when their group is removed.
{% ifversion ghes > 3.1 or ghae or ghec %}
{% data reusables.github-actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
{% data reusables.actions.self-hosted-runner-groups-navigate-to-repo-org-enterprise %}
1. In the list of groups, to the right of the group you want to delete, click {% octicon "kebab-horizontal" aria-label="The horizontal kebab icon" %}.
2. To remove the group, click **Remove group**.
3. Review the confirmation prompts, and click **Remove this runner group**.

10
content/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners.md
View File

@@ -21,10 +21,10 @@ shortTitle: Monitor & troubleshoot
## Checking the status of a self-hosted runner
{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
{% data reusables.actions.self-hosted-runner-management-permissions-required %}
{% data reusables.github-actions.self-hosted-runner-navigate-repo-and-org %}
{% data reusables.github-actions.settings-sidebar-actions-runners %}
{% data reusables.actions.self-hosted-runner-navigate-repo-and-org %}
{% data reusables.actions.settings-sidebar-actions-runners %}
1. Under {% ifversion fpt or ghes > 3.1 or ghae or ghec %}"Runners"{% else %}"Self-hosted runners"{% endif %}, you can view a list of registered runners, including the runner's name, labels, and status.
The status can be one of the following:
@@ -46,12 +46,12 @@ For example:
{% mac %}
{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endmac %}
{% linux %}
{% data reusables.github-actions.self-hosted-runner-check-mac-linux %}
{% data reusables.actions.self-hosted-runner-check-mac-linux %}
{% endlinux %}
{% windows %}

48
content/actions/hosting-your-own-runners/removing-self-hosted-runners.md
View File

@@ -21,54 +21,54 @@ shortTitle: Remove self-hosted runners
{% note %}
**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
{% data reusables.github-actions.self-hosted-runner-auto-removal %}
{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
To remove a self-hosted runner from a user repository you must be the repository owner. For an organization repository, you must be an organization owner or have admin access to the repository. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
{% data reusables.github-actions.self-hosted-runner-reusing %}
{% data reusables.actions.self-hosted-runner-reusing %}
{% 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.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
{% data reusables.actions.settings-sidebar-actions %}
{% data reusables.actions.settings-sidebar-actions-runners-updated %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% 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.github-actions.self-hosted-runner-removing-a-runner %}
{% data reusables.actions.settings-sidebar-actions-runners %}
{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Removing a runner from an organization
{% note %}
**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
{% data reusables.github-actions.self-hosted-runner-auto-removal %}
{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
To remove a self-hosted runner from an organization, you must be an organization owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see "[Self-hosted runners](/rest/reference/actions#self-hosted-runners)."
{% data reusables.github-actions.self-hosted-runner-reusing %}
{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion fpt or ghes > 3.3 or ghec %}
{% 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.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
{% data reusables.actions.settings-sidebar-actions %}
{% data reusables.actions.settings-sidebar-actions-runners-updated %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghes < 3.4 or ghae %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.settings-sidebar-actions-runners %}
{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
{% data reusables.actions.settings-sidebar-actions-runners %}
{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
## Removing a runner from an enterprise
@@ -79,27 +79,27 @@ If you use {% data variables.product.prodname_ghe_cloud %}, you can also remove
{% ifversion ghec or ghes or ghae %}
{% note %}
**Note:** {% data reusables.github-actions.self-hosted-runner-removal-impact %}
**Note:** {% data reusables.actions.self-hosted-runner-removal-impact %}
{% data reusables.github-actions.self-hosted-runner-auto-removal %}
{% data reusables.actions.self-hosted-runner-auto-removal %}
{% endnote %}
To remove a self-hosted runner from an enterprise, you must be an enterprise owner. We recommend that you also have access to the self-hosted runner machine. For information about how to remove a self-hosted runner with the REST API, see the enterprise endpoints in the [{% data variables.product.prodname_actions %} REST API](/rest/reference/actions#self-hosted-runners).
{% data reusables.github-actions.self-hosted-runner-reusing %}
{% data reusables.actions.self-hosted-runner-reusing %}
{% ifversion ghec or ghes > 3.3 or ghae-issue-5091 %}
{% 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 %}
{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.github-actions.self-hosted-runner-removing-a-runner-updated %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.self-hosted-runner-removing-a-runner-updated %}
{% elsif ghae or ghes < 3.4 %}
{% 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 %}
{% data reusables.github-actions.self-hosted-runner-removing-a-runner %}
{% data reusables.actions.self-hosted-runner-removing-a-runner %}
{% endif %}
{% endif %}

48
content/actions/hosting-your-own-runners/using-labels-with-self-hosted-runners.md
View File

@@ -16,55 +16,55 @@ shortTitle: Label runners
For information on how to use labels to route jobs to specific types of self-hosted runners, see "[Using self-hosted runners in a workflow](/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow)."
{% data reusables.github-actions.self-hosted-runner-management-permissions-required %}
{% data reusables.actions.self-hosted-runner-management-permissions-required %}
## Creating a custom label
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
1. In the "Labels" section, click {% octicon "gear" aria-label="The Gear icon" %}.
1. In the "Find or create a label" field, type the name of your new label and click **Create new label**.
The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.actions.actions-unused-labels %}
{% elsif ghae or ghes < 3.4 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.self-hosted-runner-list %}
{% data reusables.github-actions.self-hosted-runner-list-group %}
{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.self-hosted-runner-list %}
{% data reusables.actions.self-hosted-runner-list-group %}
{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. In the "Filter labels" field, type the name of your new label, and click **Create new label**.
![Add runner label](/assets/images/help/settings/actions-add-runner-label.png)
The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.github-actions.actions-unused-labels %}
The custom label is created and assigned to the self-hosted runner. Custom labels can be removed from self-hosted runners, but they currently can't be manually deleted. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Assigning a label to a self-hosted runner
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.github-actions.runner-label-settings %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.runner-label-settings %}
1. To assign a label to your self-hosted runner, in the "Find or create a label" field, click the label.
{% elsif ghae or ghes < 3.4 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.self-hosted-runner-list %}
{% data reusables.github-actions.self-hosted-runner-list-group %}
{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.self-hosted-runner-list %}
{% data reusables.actions.self-hosted-runner-list-group %}
{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. Click on a label to assign it to your self-hosted runner.
{% endif %}
## Removing a custom label from a self-hosted runner
{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5091 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.settings-sidebar-actions-runner-selection %}
{% data reusables.github-actions.runner-label-settings %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.settings-sidebar-actions-runner-selection %}
{% data reusables.actions.runner-label-settings %}
1. In the "Find or create a label" field, assigned labels are marked with the {% octicon "check" aria-label="The Check icon" %} icon. Click on a marked label to unassign it from your self-hosted runner.
{% elsif ghae or ghes < 3.4 %}
{% data reusables.github-actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.self-hosted-runner-list %}
{% data reusables.github-actions.self-hosted-runner-list-group %}
{% data reusables.github-actions.self-hosted-runner-labels-view-assigned-labels %}
1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.github-actions.actions-unused-labels %}
{% data reusables.actions.self-hosted-runner-navigate-to-repo-org-enterprise %}
{% data reusables.actions.self-hosted-runner-list %}
{% data reusables.actions.self-hosted-runner-list-group %}
{% data reusables.actions.self-hosted-runner-labels-view-assigned-labels %}
1. Click on the assigned label to remove it from your self-hosted runner. {% data reusables.actions.actions-unused-labels %}
{% endif %}
## Using the configuration script to create and assign labels

2
content/actions/hosting-your-own-runners/using-self-hosted-runners-in-a-workflow.md
View File

@@ -23,7 +23,7 @@ For information on creating custom and default labels, see "[Using labels with s
Labels allow you to send workflow jobs to specific types of self-hosted runners, based on their shared characteristics. For example, if your job requires a particular hardware component or software package, you can assign a custom label to a runner and then configure your job to only execute on runners with that label.
{% data reusables.github-actions.self-hosted-runner-labels-runs-on %}
{% data reusables.actions.self-hosted-runner-labels-runs-on %}
For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idruns-on)."

18
content/actions/learn-github-actions/contexts.md
View File

@@ -31,7 +31,7 @@ You can access contexts using the expression syntax. For more information, see "
`${{ <context> }}`
{% endraw %}
{% data reusables.github-actions.context-injection-warning %}
{% data reusables.actions.context-injection-warning %}
| Context name | Type | Description |
|---------------|------|-------------|
@@ -59,7 +59,7 @@ In order to use property dereference syntax, the property name must:
### Determining when to use contexts
{% data reusables.github-actions.using-context-or-environment-variables %}
{% data reusables.actions.using-context-or-environment-variables %}
### Context availability
@@ -142,7 +142,7 @@ The following table indicates where each context and special function can be use
You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
{% data reusables.github-actions.github-context-warning %}
{% data reusables.actions.github-context-warning %}
{% raw %}
```yaml{:copy}
@@ -173,8 +173,8 @@ jobs:
The `github` context contains information about the workflow run and the event that triggered the run. You can also read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
{% data reusables.github-actions.github-context-warning %}
{% data reusables.github-actions.context-injection-warning %}
{% data reusables.actions.github-context-warning %}
{% data reusables.actions.context-injection-warning %}
| Property name | Type | Description |
|---------------|------|-------------|
@@ -204,8 +204,8 @@ The `github` context contains information about the workflow run and the event t
| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
| `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. |
| `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. |
| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
| `github.run_id` | `string` | {% data reusables.actions.run_id_description %} |
| `github.run_number` | `string` | {% data reusables.actions.run_number_description %} |
| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
@@ -527,7 +527,7 @@ The `secrets` context contains the names and values of secrets that are availabl
`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
{% data reusables.github-actions.secrets-redaction-warning %}
{% data reusables.actions.secrets-redaction-warning %}
| Property name | Type | Description |
|---------------|------|-------------|
@@ -549,7 +549,7 @@ The following example contents of the `secrets` context shows the automatic `GIT
### Example usage of the `secrets` context
{% data reusables.github-actions.github_token-input-example %}
{% data reusables.actions.github_token-input-example %}
## `strategy` context

4
content/actions/learn-github-actions/environment-variables.md
View File

@@ -153,8 +153,8 @@ We strongly recommend that actions use environment variables to access the files
| `GITHUB_REPOSITORY_OWNER` | The repository owner's name. For example, `octocat`. |
| `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. |
| `GITHUB_RUN_ATTEMPT` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. For example, `3`. |
| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} For example, `1658821493`. |
| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} For example, `3`. |
| `GITHUB_RUN_ID` | {% data reusables.actions.run_id_description %} For example, `1658821493`. |
| `GITHUB_RUN_NUMBER` | {% data reusables.actions.run_number_description %} For example, `3`. |
| `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.
| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
| `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. |

4
content/actions/learn-github-actions/expressions.md
View File

@@ -25,9 +25,9 @@ You need to use specific syntax to tell {% data variables.product.prodname_dotco
`${{ <expression> }}`
{% endraw %}
{% data reusables.github-actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
{% data reusables.actions.expression-syntax-if %} For more information about `if` conditionals, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idif)."
{% data reusables.github-actions.context-injection-warning %}
{% data reusables.actions.context-injection-warning %}
#### Example expression in an `if` conditional

2
content/actions/learn-github-actions/understanding-github-actions.md
View File

@@ -261,7 +261,7 @@ To understand how billing works for {% data variables.product.prodname_actions %
## Contacting support
{% data reusables.github-actions.contacting-support %}
{% data reusables.actions.contacting-support %}
## Further reading

12
content/actions/learn-github-actions/usage-limits-billing-and-administration.md
View File

@@ -21,7 +21,7 @@ shortTitle: Workflow billing & limits
{% data reusables.repositories.about-github-actions %} For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions){% ifversion fpt %}."{% elsif ghes or ghec %}" and "[About {% data variables.product.prodname_actions %} for enterprises](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/about-github-actions-for-enterprises)."{% endif %}
{% ifversion fpt or ghec %}
{% data reusables.github-actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
{% data reusables.actions.actions-billing %} For more information, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."
{% else %}
GitHub Actions usage is free for {% data variables.product.prodname_ghe_server %} instances that use self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
{% endif %}
@@ -47,8 +47,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
{% endnote %}
- **Job execution time** - Each job in a workflow can run for up to 6 hours of execution time. If a job reaches this limit, the job is terminated and fails to complete.
{% data reusables.github-actions.usage-workflow-run-time %}
{% data reusables.github-actions.usage-api-requests %}
{% data reusables.actions.usage-workflow-run-time %}
{% data reusables.actions.usage-api-requests %}
- **Concurrent jobs** - The number of concurrent jobs you can run in your account depends on your GitHub plan, as indicated in the following table. If exceeded, any additional jobs are queued.
| GitHub plan | Total concurrent jobs | Maximum concurrent macOS jobs |
@@ -57,8 +57,8 @@ There are some limits on {% data variables.product.prodname_actions %} usage whe
| Pro | 40 | 5 |
| Team | 60 | 5 |
| Enterprise | 180 | 50 |
- **Job matrix** - {% data reusables.github-actions.usage-matrix-limits %}
{% data reusables.github-actions.usage-workflow-queue-limits %}
- **Job matrix** - {% data reusables.actions.usage-matrix-limits %}
{% data reusables.actions.usage-workflow-queue-limits %}
{% else %}
Usage limits apply to self-hosted runners. For more information, see "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners/#usage-limits)."
@@ -94,7 +94,7 @@ For more information, see:
## Disabling or limiting {% data variables.product.prodname_actions %} for your repository or organization
{% data reusables.github-actions.disabling-github-actions %}
{% data reusables.actions.disabling-github-actions %}
For more information, see:
- "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository)"

2
content/actions/managing-workflow-runs/removing-workflow-artifacts.md
View File

@@ -22,7 +22,7 @@ shortTitle: Remove workflow artifacts
{% data reusables.repositories.permissions-statement-write %}
{% data reusables.github-actions.artifact-log-retention-statement %}
{% data reusables.actions.artifact-log-retention-statement %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.actions-tab %}

2
content/actions/migrating-to-github-actions/migrating-from-travis-ci-to-github-actions.md
View File

@@ -180,7 +180,7 @@ git:
Travis CI and {% data variables.product.prodname_actions %} can both add custom environment variables to a test matrix, which allows you to refer to the variable in a later step.
In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.github-actions.matrix-variable-example %}
In {% data variables.product.prodname_actions %}, you can use the `include` key to add custom environment variables to a matrix. {% data reusables.actions.matrix-variable-example %}
## Key features in {% data variables.product.prodname_actions %}

2
content/actions/monitoring-and-troubleshooting-workflows/about-monitoring-and-troubleshooting.md
View File

@@ -18,7 +18,7 @@ miniTocMaxHeadingLevel: 3
{% if github-runner-dashboard %}
### Monitoring your current jobs in your organization or enterprise
{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}

8
content/actions/monitoring-and-troubleshooting-workflows/enabling-debug-logging.md
View File

@@ -15,12 +15,12 @@ versions:
These extra logs are enabled by setting secrets in the repository containing the workflow, so the same permissions requirements will apply:
- {% data reusables.github-actions.permissions-statement-secrets-repository %}
- {% data reusables.actions.permissions-statement-secrets-repository %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
- {% data reusables.github-actions.permissions-statement-secrets-environment %}
- {% data reusables.actions.permissions-statement-secrets-environment %}
{% endif %}
- {% data reusables.github-actions.permissions-statement-secrets-organization %}
- {% data reusables.github-actions.permissions-statement-secrets-api %}
- {% data reusables.actions.permissions-statement-secrets-organization %}
- {% data reusables.actions.permissions-statement-secrets-api %}
For more information on setting secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."

2
content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md
View File

@@ -19,7 +19,7 @@ If the run is complete, you can see whether the result was a success, failure, c
{% data variables.product.prodname_actions %} use the Checks API to output statuses, results, and logs for a workflow. {% data variables.product.prodname_dotcom %} creates a new check suite for each workflow run. The check suite contains a check run for each job in the workflow, and each job includes steps. {% data variables.product.prodname_actions %} are run as a step in a workflow. For more information about the Checks API, see "[Checks](/rest/reference/checks)."
{% data reusables.github-actions.invalid-workflow-files %}
{% data reusables.actions.invalid-workflow-files %}
## Viewing logs to diagnose failures

4
content/actions/publishing-packages/publishing-docker-images.md
View File

@@ -50,7 +50,7 @@ In this guide, we will use the Docker `build-push-action` action to build the Do
## Publishing images to Docker Hub
{% data reusables.github-actions.release-trigger-workflow %}
{% data reusables.actions.release-trigger-workflow %}
In the example workflow below, we use the Docker `login-action` and `build-push-action` actions to build the Docker image and, if the build succeeds, push the built image to Docker Hub.
@@ -108,7 +108,7 @@ The above workflow checks out the {% data variables.product.prodname_dotcom %} r
## Publishing images to {% data variables.product.prodname_registry %}
{% data reusables.github-actions.release-trigger-workflow %}
{% data reusables.actions.release-trigger-workflow %}
In the example workflow below, we use the Docker `login-action`{% ifversion fpt or ghec %}, `metadata-action`,{% endif %} and `build-push-action` actions to build the Docker image, and if the build succeeds, push the built image to {% data variables.product.prodname_registry %}.

10
content/actions/publishing-packages/publishing-java-packages-with-gradle.md
View File

@@ -23,7 +23,7 @@ shortTitle: Java packages with Gradle
## Introduction
{% data reusables.github-actions.publishing-java-packages-intro %}
{% data reusables.actions.publishing-java-packages-intro %}
## Prerequisites
@@ -104,7 +104,7 @@ jobs:
MAVEN_PASSWORD: {% raw %}${{ secrets.OSSRH_TOKEN }}{% endraw %}
```
{% data reusables.github-actions.gradle-workflow-steps %}
{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret.
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
@@ -115,7 +115,7 @@ Each time you create a new release, you can trigger a workflow to publish your p
You can define a new Maven repository in the publishing block of your _build.gradle_ that points to {% data variables.product.prodname_registry %}. In that repository configuration, you can also take advantage of environment variables set in your CI workflow run. You can use the `GITHUB_ACTOR` environment variable as a username, and you can set the `GITHUB_TOKEN` environment variable with your `GITHUB_TOKEN` secret.
{% data reusables.github-actions.github-token-permissions %}
{% data reusables.actions.github-token-permissions %}
For example, if your organization is named "octocat" and your repository is named "hello-world", then the {% data variables.product.prodname_registry %} configuration in _build.gradle_ would look similar to the below example.
@@ -174,7 +174,7 @@ jobs:
GITHUB_TOKEN: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
{% data reusables.github-actions.gradle-workflow-steps %}
{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to {% data variables.product.prodname_registry %}. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
@@ -255,7 +255,7 @@ jobs:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}{% endraw %}
```
{% data reusables.github-actions.gradle-workflow-steps %}
{% data reusables.actions.gradle-workflow-steps %}
1. Runs the [`gradle/gradle-build-action`](https://github.com/gradle/gradle-build-action) action with the `publish` argument to publish to the `OSSRH` Maven repository and {% data variables.product.prodname_registry %}. The `MAVEN_USERNAME` environment variable will be set with the contents of your `OSSRH_USERNAME` secret, and the `MAVEN_PASSWORD` environment variable will be set with the contents of your `OSSRH_TOKEN` secret. The `GITHUB_TOKEN` environment variable will be set with the content of the `GITHUB_TOKEN` secret. {% ifversion fpt or ghes > 3.1 or ghae or ghec %}The `permissions` key specifies the access that the `GITHUB_TOKEN` secret will allow.{% endif %}
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."

12
content/actions/publishing-packages/publishing-java-packages-with-maven.md
View File

@@ -23,7 +23,7 @@ shortTitle: Java packages with Maven
## Introduction
{% data reusables.github-actions.publishing-java-packages-intro %}
{% data reusables.actions.publishing-java-packages-intro %}
## Prerequisites
@@ -105,7 +105,7 @@ This workflow performs the following steps:
1. Checks out a copy of project's repository.
1. Sets up the Java JDK, and also configures the Maven _settings.xml_ file to add authentication for the `ossrh` repository using the `MAVEN_USERNAME` and `MAVEN_PASSWORD` environment variables.
1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
1. {% data reusables.actions.publish-to-maven-workflow-step %}
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
@@ -115,7 +115,7 @@ Each time you create a new release, you can trigger a workflow to publish your p
In this workflow, you can use the `setup-java` action. This action installs the given version of the JDK into the `PATH`, and also sets up a Maven _settings.xml_ for publishing the package to {% data variables.product.prodname_registry %}. The generated _settings.xml_ defines authentication for a server with an `id` of `github`, using the `GITHUB_ACTOR` environment variable as the username and the `GITHUB_TOKEN` environment variable as the password. The `GITHUB_TOKEN` environment variable is assigned the value of the special `GITHUB_TOKEN` secret.
{% data reusables.github-actions.github-token-permissions %}
{% data reusables.actions.github-token-permissions %}
For a Maven-based project, you can make use of these settings by creating a distribution repository in your _pom.xml_ file with an `id` of `github` that points to your {% data variables.product.prodname_registry %} endpoint.
@@ -165,7 +165,7 @@ This workflow performs the following steps:
1. Checks out a copy of project's repository.
1. Sets up the Java JDK, and also automatically configures the Maven _settings.xml_ file to add authentication for the `github` Maven repository to use the `GITHUB_TOKEN` environment variable.
1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
1. {% data reusables.actions.publish-to-packages-workflow-step %}
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."
@@ -218,8 +218,8 @@ This workflow performs the following steps:
1. Checks out a copy of project's repository.
1. Calls `setup-java` the first time. This configures the Maven _settings.xml_ file for the `ossrh` repository, and sets the authentication options to environment variables that are defined in the next step.
1. {% data reusables.github-actions.publish-to-maven-workflow-step %}
1. {% data reusables.actions.publish-to-maven-workflow-step %}
1. Calls `setup-java` the second time. This automatically configures the Maven _settings.xml_ file for {% data variables.product.prodname_registry %}.
1. {% data reusables.github-actions.publish-to-packages-workflow-step %}
1. {% data reusables.actions.publish-to-packages-workflow-step %}
For more information about using secrets in your workflow, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)."

4
content/actions/publishing-packages/publishing-nodejs-packages.md
View File

@@ -43,7 +43,7 @@ You may also find it helpful to have a basic understanding of the following:
The `name` and `version` fields in the *package.json* file create a unique identifier that registries use to link your package to a registry. You can add a summary for the package listing page by including a `description` field in the *package.json* file. For more information, see "[Creating a package.json file](https://docs.npmjs.com/creating-a-package-json-file)" and "[Creating Node.js modules](https://docs.npmjs.com/creating-node-js-modules)" in the npm documentation.
When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.github-actions.setup-node-intro %}
When a local *.npmrc* file exists and has a `registry` value specified, the `npm publish` command uses the registry configured in the *.npmrc* file. {% data reusables.actions.setup-node-intro %}
You can specify the Node.js version installed on the runner using the `setup-node` action.
@@ -115,7 +115,7 @@ However, if you do provide the `repository` key, then the repository in that key
### Authenticating to the destination repository
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.github-actions.github-token-permissions %}
To perform authenticated operations against the {% data variables.product.prodname_registry %} registry in your workflow, you can use the `GITHUB_TOKEN`. {% data reusables.actions.github-token-permissions %}
If you want to publish your package to a different repository, you must use a personal access token (PAT) that has permission to write to packages in the destination repository. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)" and "[Encrypted secrets](/actions/reference/encrypted-secrets)."

6
content/actions/security-guides/automatic-token-authentication.md
View File

@@ -39,11 +39,11 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
{% endnote %}
{% endif %}
{% data reusables.github-actions.actions-do-not-trigger-workflows %}
{% data reusables.actions.actions-do-not-trigger-workflows %}
### Example 1: passing the `GITHUB_TOKEN` as an input
{% data reusables.github-actions.github_token-input-example %}
{% data reusables.actions.github_token-input-example %}
### Example 2: calling the REST API
@@ -123,7 +123,7 @@ You can see the permissions that `GITHUB_TOKEN` had for a specific job in the "S
You can use the `permissions` key in your workflow file to modify permissions for the `GITHUB_TOKEN` for an entire workflow or for individual jobs. This allows you to configure the minimum required permissions for a workflow or job. When the `permissions` key is used, all unspecified permissions are set to no access, with the exception of the `metadata` scope, which always gets read access.
{% data reusables.github-actions.forked-write-permission %}
{% data reusables.actions.forked-write-permission %}
The two workflow examples earlier in this article show the `permissions` key being used at the workflow level, and at the job level. In [Example 1](#example-1-passing-the-github_token-as-an-input) the two permissions are specified for the entire workflow. In [Example 2](#example-2-calling-the-rest-api) write access is granted for one scope for a single job.

18
content/actions/security-guides/encrypted-secrets.md
View File

@@ -21,7 +21,7 @@ versions:
Secrets are encrypted environment variables that you create in an organization{% ifversion fpt or ghes > 3.0 or ghae or ghec %}, repository, or repository environment{% else %} or repository{% endif %}. The secrets that you create are available to use in {% data variables.product.prodname_actions %} workflows. {% data variables.product.prodname_dotcom %} uses a [libsodium sealed box](https://libsodium.gitbook.io/doc/public-key_cryptography/sealed_boxes) to help ensure that secrets are encrypted before they reach {% data variables.product.prodname_dotcom %} and remain encrypted until you use them in a workflow.
{% data reusables.github-actions.secrets-org-level-overview %}
{% data reusables.actions.secrets-org-level-overview %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
For secrets stored at the environment level, you can enable required reviewers to control access to the secrets. A workflow job cannot access environment secrets until approval is granted by required approvers.
@@ -53,7 +53,7 @@ To make a secret available to an action, you must set the secret as an input or
You can use and read encrypted secrets in a workflow file if you have access to edit the file. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
{% data reusables.github-actions.secrets-redaction-warning %}
{% data reusables.actions.secrets-redaction-warning %}
{% ifversion fpt or ghes > 3.0 or ghae or ghec %}
Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
@@ -73,13 +73,13 @@ When generating credentials, we recommend that you grant the minimum permissions
## Creating encrypted secrets for a repository
{% data reusables.github-actions.permissions-statement-secrets-repository %}
{% data reusables.actions.permissions-statement-secrets-repository %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
1. Click **New repository secret**.
1. Type a name for your secret in the **Name** input box.
1. Enter the value for your secret.
@@ -113,13 +113,13 @@ To list all secrets for the repository, use the `gh secret list` subcommand.
## Creating encrypted secrets for an environment
{% data reusables.github-actions.permissions-statement-secrets-environment %}
{% data reusables.actions.permissions-statement-secrets-environment %}
{% webui %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.github-actions.sidebar-environment %}
{% data reusables.actions.sidebar-environment %}
1. Click on the environment that you want to add a secret to.
2. Under **Environment secrets**, click **Add secret**.
3. Type a name for your secret in the **Name** input box.
@@ -150,13 +150,13 @@ gh secret list --env <em>environment-name</em>
When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
{% data reusables.github-actions.permissions-statement-secrets-organization %}
{% data reusables.actions.permissions-statement-secrets-organization %}
{% webui %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
1. Click **New organization secret**.
1. Type a name for your secret in the **Name** input box.
1. Enter the **Value** for your secret.
@@ -209,7 +209,7 @@ You can check which access policies are being applied to a secret in your organi
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
1. The list of secrets includes any configured permissions and policies. For example:
![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
1. For more details on the configured permissions for each secret, click **Update**.

2
content/actions/using-containerized-services/about-service-containers.md
View File

@@ -25,7 +25,7 @@ Service containers are Docker containers that provide a simple and portable way
You can configure service containers for each job in a workflow. {% data variables.product.prodname_dotcom %} creates a fresh Docker container for each service configured in the workflow, and destroys the service container when the job completes. Steps in a job can communicate with all service containers that are part of the same job.
{% data reusables.github-actions.docker-container-os-support %}
{% data reusables.actions.docker-container-os-support %}
## Communicating with service containers

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

@@ -24,11 +24,11 @@ topics:
This guide shows you workflow examples that configure a service container using the Docker Hub `postgres` image. The workflow runs a script that connects to the PostgreSQL service, creates a table, and then populates it with data. To test that the workflow creates and populates the PostgreSQL table, the script prints the data from the table to the console.
{% data reusables.github-actions.docker-container-os-support %}
{% data reusables.actions.docker-container-os-support %}
## Prerequisites
{% data reusables.github-actions.service-container-prereqs %}
{% data reusables.actions.service-container-prereqs %}
You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and PostgreSQL. For more information, see:
@@ -37,9 +37,9 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f
## Running jobs in containers
{% data reusables.github-actions.container-jobs-intro %}
{% data reusables.actions.container-jobs-intro %}
{% data reusables.github-actions.copy-workflow-file %}
{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -95,9 +95,9 @@ jobs:
### Configuring the runner job
{% data reusables.github-actions.service-container-host %}
{% data reusables.actions.service-container-host %}
{% data reusables.github-actions.postgres-label-description %}
{% data reusables.actions.postgres-label-description %}
```yaml{:copy}
jobs:
@@ -127,7 +127,7 @@ jobs:
### Configuring the steps
{% data reusables.github-actions.service-template-steps %}
{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -153,7 +153,7 @@ steps:
POSTGRES_PORT: 5432
```
{% data reusables.github-actions.postgres-environment-variables %}
{% data reusables.actions.postgres-environment-variables %}
The hostname of the PostgreSQL service is the label you configured in your workflow, in this case, `postgres`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default PostgreSQL port 5432.
@@ -161,7 +161,7 @@ The hostname of the PostgreSQL service is the label you configured in your workf
When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
{% data reusables.github-actions.copy-workflow-file %}
{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -219,9 +219,9 @@ jobs:
### Configuring the runner job
{% data reusables.github-actions.service-container-host-runner %}
{% data reusables.actions.service-container-host-runner %}
{% data reusables.github-actions.postgres-label-description %}
{% data reusables.actions.postgres-label-description %}
The workflow maps port 5432 on the PostgreSQL service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
@@ -254,7 +254,7 @@ jobs:
### Configuring the steps
{% data reusables.github-actions.service-template-steps %}
{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -280,9 +280,9 @@ steps:
POSTGRES_PORT: 5432
```
{% data reusables.github-actions.postgres-environment-variables %}
{% data reusables.actions.postgres-environment-variables %}
{% data reusables.github-actions.service-container-localhost %}
{% data reusables.actions.service-container-localhost %}
## Testing the PostgreSQL service container
@@ -290,7 +290,7 @@ You can test your workflow using the following script, which connects to the Pos
You can modify *client.js* to include any PostgreSQL operations needed by your workflow. In this example, the script connects to the PostgreSQL service, adds a table to the `postgres` database, inserts some placeholder data, and then retrieves the data.
{% data reusables.github-actions.service-container-add-script %}
{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const { Client } = require('pg');

30
content/actions/using-containerized-services/creating-redis-service-containers.md
View File

@@ -24,11 +24,11 @@ topics:
This guide shows you workflow examples that configure a service container using the Docker Hub `redis` image. The workflow runs a script to create a Redis client and populate the client with data. To test that the workflow creates and populates the Redis client, the script prints the client's data to the console.
{% data reusables.github-actions.docker-container-os-support %}
{% data reusables.actions.docker-container-os-support %}
## Prerequisites
{% data reusables.github-actions.service-container-prereqs %}
{% data reusables.actions.service-container-prereqs %}
You may also find it helpful to have a basic understanding of YAML, the syntax for {% data variables.product.prodname_actions %}, and Redis. For more information, see:
@@ -37,9 +37,9 @@ You may also find it helpful to have a basic understanding of YAML, the syntax f
## Running jobs in containers
{% data reusables.github-actions.container-jobs-intro %}
{% data reusables.actions.container-jobs-intro %}
{% data reusables.github-actions.copy-workflow-file %}
{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -92,9 +92,9 @@ jobs:
### Configuring the container job
{% data reusables.github-actions.service-container-host %}
{% data reusables.actions.service-container-host %}
{% data reusables.github-actions.redis-label-description %}
{% data reusables.actions.redis-label-description %}
```yaml{:copy}
jobs:
@@ -121,7 +121,7 @@ jobs:
### Configuring the steps
{% data reusables.github-actions.service-template-steps %}
{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -146,7 +146,7 @@ steps:
REDIS_PORT: 6379
```
{% data reusables.github-actions.redis-environment-variables %}
{% data reusables.actions.redis-environment-variables %}
The hostname of the Redis service is the label you configured in your workflow, in this case, `redis`. Because Docker containers on the same user-defined bridge network open all ports by default, you'll be able to access the service container on the default Redis port 6379.
@@ -154,7 +154,7 @@ The hostname of the Redis service is the label you configured in your workflow,
When you run a job directly on the runner machine, you'll need to map the ports on the service container to ports on the Docker host. You can access service containers from the Docker host using `localhost` and the Docker host port number.
{% data reusables.github-actions.copy-workflow-file %}
{% data reusables.actions.copy-workflow-file %}
{% raw %}
```yaml{:copy}
@@ -209,9 +209,9 @@ jobs:
### Configuring the runner job
{% data reusables.github-actions.service-container-host-runner %}
{% data reusables.actions.service-container-host-runner %}
{% data reusables.github-actions.redis-label-description %}
{% data reusables.actions.redis-label-description %}
The workflow maps port 6379 on the Redis service container to the Docker host. For more information about the `ports` keyword, see "[About service containers](/actions/automating-your-workflow-with-github-actions/about-service-containers#mapping-docker-host-and-service-container-ports)."
@@ -241,7 +241,7 @@ jobs:
### Configuring the steps
{% data reusables.github-actions.service-template-steps %}
{% data reusables.actions.service-template-steps %}
```yaml{:copy}
steps:
@@ -267,9 +267,9 @@ steps:
REDIS_PORT: 6379
```
{% data reusables.github-actions.redis-environment-variables %}
{% data reusables.actions.redis-environment-variables %}
{% data reusables.github-actions.service-container-localhost %}
{% data reusables.actions.service-container-localhost %}
## Testing the Redis service container
@@ -277,7 +277,7 @@ You can test your workflow using the following script, which creates a Redis cli
You can modify *client.js* to include any Redis operations needed by your workflow. In this example, the script creates the Redis client instance, adds placeholder data, then retrieves the data.
{% data reusables.github-actions.service-container-add-script %}
{% data reusables.actions.service-container-add-script %}
```javascript{:copy}
const redis = require("redis");

6
content/actions/using-github-hosted-runners/about-github-hosted-runners.md
View File

@@ -29,7 +29,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
{% ifversion not ghes %}
{% data reusables.github-actions.runner-app-open-source %}
{% data reusables.actions.runner-app-open-source %}
### Cloud hosts for {% data variables.product.prodname_dotcom %}-hosted runners
@@ -39,7 +39,7 @@ You can specify the runner type for each job in a workflow. Each job in a workfl
### Workflow continuity for {% data variables.product.prodname_dotcom %}-hosted runners
{% data reusables.github-actions.runner-workflow-continuity %}
{% data reusables.actions.runner-workflow-continuity %}
In addition, if the workflow run has been successfully queued, but has not been processed by a {% data variables.product.prodname_dotcom %}-hosted runner within 45 minutes, then the queued workflow run is discarded.
@@ -61,7 +61,7 @@ Hardware specification for macOS virtual machines:
- 14 GB of RAM memory
- 14 GB of SSD disk space
{% data reusables.github-actions.supported-github-runners %}
{% data reusables.actions.supported-github-runners %}
Workflow logs list the runner used to run a job. For more information, see "[Viewing workflow run history](/actions/managing-workflow-runs/viewing-workflow-run-history)."

8
content/actions/using-github-hosted-runners/monitoring-your-current-jobs.md
View File

@@ -13,8 +13,8 @@ shortTitle: Monitoring your current jobs
You can get a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners in your organization or enterprise.
{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.github-hosted-runners-table-entry %}
{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "Active jobs" section, which contains a list of all jobs currently running on {% data variables.product.prodname_dotcom %}-hosted runners.
![Screenshot of the list of active jobs](/assets/images/help/settings/actions-runner-active-jobs.png)
@@ -25,7 +25,7 @@ You can get a list of all jobs currently running on {% data variables.product.pr
The following procedure demonstrates how to check the maximum number of concurrent jobs you can run.
{% data reusables.github-actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
{% data reusables.github-actions.github-hosted-runners-table-entry %}
{% data reusables.actions.github-hosted-runners-navigate-to-repo-org-enterprise %}
{% data reusables.actions.github-hosted-runners-table-entry %}
1. Review the "All jobs usage" section, which lists the number of active jobs and the maximum number of jobs you can run. In this example, `9` jobs are currently running out of a maximum of `180`.
![Screenshot of the maximum jobs for an account](/assets/images/help/settings/github-hosted-runners-max-jobs.png)

2
content/actions/using-jobs/using-concurrency.md
View File

@@ -20,5 +20,5 @@ miniTocMaxHeadingLevel: 4
{% if github-runner-dashboard %}
## Monitoring your current jobs in your organization or enterprise
{% data reusables.github-actions.github-hosted-runners-check-concurrency %}
{% data reusables.actions.github-hosted-runners-check-concurrency %}
{% endif %}

56
content/actions/using-workflows/events-that-trigger-workflows.md
View File

@@ -37,7 +37,7 @@ Some events have multiple activity types. For these events, you can specify whic
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when branch protection rules in the workflow repository are changed. For more information about branch protection rules, see "[About protected branches](/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches)." For information about the branch protection rule APIs, see "[BranchProtectionRule](/graphql/reference/objects#branchprotectionrule)" in the GraphQL API documentation or "[Branches](/rest/reference/branches)" in the REST API documentation.
@@ -64,7 +64,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to a check run occurs. A check run is an individual test that is part of a check suite. For information, see "[Getting started with the Checks API](/rest/guides/getting-started-with-the-checks-api)." For information about the check run APIs, see "[CheckRun](/graphql/reference/objects#checkrun)" in the GraphQL API documentation or "[Checks](/rest/reference/checks#runs)" in the REST API documentation.
@@ -88,7 +88,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}
@@ -133,7 +133,7 @@ on:
| --------------------- | -------------- | ------------ | -------------|
| [`delete`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#delete) | n/a | Last commit on default branch | Default branch |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}
@@ -199,7 +199,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -225,7 +225,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% data reusables.webhooks.discussions-webhooks-beta %}
@@ -247,7 +247,7 @@ on:
| --------------------- | -------------- | ------------ | -------------|
| [`fork`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#fork) | n/a | Last commit on default branch | Default branch |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when someone forks a repository. For information about the REST API, see "[Create a fork](/rest/reference/repos#create-a-fork)."
@@ -264,7 +264,7 @@ on:
| --------------------- | -------------- | ------------ | -------------|
| [`gollum`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#gollum) | n/a | Last commit on default branch | Default branch |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when someone creates or updates a Wiki page. For more information, see "[About wikis](/communities/documenting-your-project-with-wikis/about-wikis)."
@@ -287,7 +287,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue or pull request comment is created, edited, or deleted. For information about the issue comment APIs, see "[IssueComment](/graphql/reference/objects#issuecomment)" in the GraphQL API documentation or "[Issue comments](/developers/webhooks-and-events/webhook-events-and-payloads#issue_comment)" in the REST API documentation.
@@ -344,7 +344,7 @@ jobs:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when an issue in the workflow's repository is created or modified. For activity related to comments in an issue, use the [`issue_comment`](#issue_comment) event. For more information about issues, see "[About issues](/issues/tracking-your-work-with-issues/about-issues)." For information about the issue APIs, see "[Issue](/graphql/reference/objects#issue)" in the GraphQL API documentation or "[Issues](/rest/reference/issues)" in the REST API documentation.
@@ -368,7 +368,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when a label in your workflow's repository is created or modified. For more information about labels, see "[Managing labels](/issues/using-labels-and-milestones-to-track-work/managing-labels)." For information about the label APIs, see "[Label](/graphql/reference/objects#label)" in the GraphQL API documentation or "[Labels](/rest/reference/issues#labels)" in the REST API documentation.
@@ -394,7 +394,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when a milestone in the workflow's repository is created or modified. For more information about milestones, see "[About milestones](/issues/using-labels-and-milestones-to-track-work/about-milestones)." For information about the milestone APIs, see "[Milestone](/graphql/reference/objects#milestone)" in the GraphQL API documentation or "[Milestones](/rest/reference/issues#milestones)" in the REST API documentation.
@@ -414,7 +414,7 @@ on:
| --------------------- | -------------- | ------------ | -------------|
| [`page_build`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#page_build) | n/a | Last commit on default branch | n/a |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when someone pushes to a branch that is the publishing source for {% data variables.product.prodname_pages %}, if {% data variables.product.prodname_pages %} is enabled for the repository. For more information about {% data variables.product.prodname_pages %} publishing sources, see "[Configuring a publishing source for your GitHub Pages site](/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#choosing-a-publishing-source)." For information about the REST API, see "[Pages](/rest/reference/repos#pages)."
@@ -437,7 +437,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}
@@ -475,7 +475,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}
@@ -513,7 +513,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}
@@ -545,7 +545,7 @@ on:
| --------------------- | -------------- | ------------ | -------------|
| [`public`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#public) | n/a | Last commit on default branch | Default branch |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when your workflow's repository changes from private to public. For information about the REST API, see "[Edit repositories](/rest/reference/repos#edit)."
@@ -625,7 +625,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -670,7 +670,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -809,7 +809,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -854,7 +854,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a pull request that includes a change to a JavaScript (`.js`) file is opened on a branch whose name starts with `releases/`:
```yaml
on:
@@ -912,7 +912,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -953,7 +953,7 @@ on:
{% note %}
**Note:** {% data reusables.github-actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
**Note:** {% data reusables.actions.branch-paths-filter %} For example, the following workflow will only run when a push that includes a change to a JavaScript (`.js`) file is made to a branch whose name starts with `releases/`:
```yaml
on:
@@ -978,7 +978,7 @@ on:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when activity related to {% data variables.product.prodname_registry %} occurs in your repository. For more information, see "[{% data variables.product.prodname_registry %} Documentation](/packages)."
@@ -1030,7 +1030,7 @@ on:
| ------------------ | ------------ | ------------ | ------------------|
| [repository_dispatch](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) | Custom | Last commit on default branch | Default branch |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
You can use the {% data variables.product.product_name %} API to trigger a webhook event called [`repository_dispatch`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#repository_dispatch) when you want to trigger a workflow for activity that happens outside of {% data variables.product.product_name %}. For more information, see "[Create a repository dispatch event](/rest/reference/repos#create-a-repository-dispatch-event)."
@@ -1122,7 +1122,7 @@ Notifications for scheduled workflows are sent to the user who last modified the
| --------------------- | -------------- | ------------ | -------------|
| [`status`](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads/#status) | n/a | Last commit on default branch | n/a |
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when the status of a Git commit changes. For example, commits can be marked as `error`, `failure`, `pending`, or `success`. If you want to provide more details about the status change, you may want to use the [`check_run`](#check_run) event. For information about the commit status APIs, see "[Status](/graphql/reference/objects#statue)" in the GraphQL API documentation or "[Statuses](/rest/reference/commits#commit-statuses)" in the REST API documentation.
@@ -1163,7 +1163,7 @@ jobs:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
Runs your workflow when the workflow's repository is starred. For information about the pull request APIs, see "[addStar](/graphql/reference/mutations#addstar)" in the GraphQL API documentation or "[Starring](/rest/reference/activity#starring)" in the REST API documentation.
@@ -1305,7 +1305,7 @@ jobs:
{% endnote %}
{% data reusables.github-actions.branch-requirement %}
{% data reusables.actions.branch-requirement %}
{% note %}

4
content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
View File

@@ -50,11 +50,11 @@ You can centrally manage your secrets within an organization, and then make them
When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
{% data reusables.github-actions.permissions-statement-secrets-organization %}
{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
1. Click **New secret**.
1. Type a name for your secret in the **Name** input box.
1. Enter the **Value** for your secret.

4
content/actions/using-workflows/storing-workflow-data-as-artifacts.md
View File

@@ -26,7 +26,7 @@ topics:
Artifacts allow you to persist data after a job has completed, and share that data with another job in the same workflow. An artifact is a file or collection of files produced during a workflow run. For example, you can use artifacts to save your build and test output after a workflow run has ended. {% data reusables.actions.reusable-workflow-artifacts %}
{% data reusables.github-actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
{% data reusables.actions.artifact-log-retention-statement %} The retention period for a pull request restarts each time someone pushes a new commit to the pull request.
These are some of the common artifacts that you can upload:
@@ -37,7 +37,7 @@ These are some of the common artifacts that you can upload:
{% ifversion fpt or ghec %}
Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.github-actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
Storing artifacts uses storage space on {% data variables.product.product_name %}. {% data reusables.actions.actions-billing %} For more information, see "[Managing billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions)."
{% else %}

14
content/actions/using-workflows/triggering-a-workflow.md
View File

@@ -41,7 +41,7 @@ The following steps occur to trigger a workflow run:
### Triggering a workflow from a workflow
{% data reusables.github-actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)."
If you do want to trigger a workflow from within a workflow run, you can use a personal access token instead of `GITHUB_TOKEN` to trigger events that require a token. You'll need to create a personal access token and store it as a secret. To minimize your {% data variables.product.prodname_actions %} usage costs, ensure that you don't create recursive or unintended workflow runs. For more information about creating a personal access token, see "[Creating a personal access token](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token)." For more information about storing a personal access token as a secret, see "[Creating and storing encrypted secrets](/actions/configuring-and-managing-workflows/creating-and-storing-encrypted-secrets)."
@@ -89,23 +89,23 @@ Use the `on` key to specify what events trigger your workflow. For more informat
### Using a single event
{% data reusables.github-actions.on-single-example %}
{% data reusables.actions.on-single-example %}
### Using multiple events
{% data reusables.github-actions.on-multiple-example %}
{% data reusables.actions.on-multiple-example %}
### Using activity types and filters with multiple events
You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.github-actions.actions-multiple-types %}
You can use activity types and filters to further control when your workflow will run. For more information, see [Using event activity types](#using-event-activity-types) and [Using filters](#using-filters). {% data reusables.actions.actions-multiple-types %}
## Using event activity types
{% data reusables.github-actions.actions-activity-types %}
{% data reusables.actions.actions-activity-types %}
## Using filters
{% data reusables.github-actions.actions-filters %}
{% data reusables.actions.actions-filters %}
### Using filters to target specific branches for pull request events
@@ -125,7 +125,7 @@ You can use activity types and filters to further control when your workflow wil
## Defining inputs for manually triggered workflows
{% data reusables.github-actions.workflow-dispatch-inputs %}
{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
## Defining inputs, outputs, and secrets for reusable workflows

8
content/actions/using-workflows/workflow-syntax-for-github-actions.md
View File

@@ -173,7 +173,7 @@ A boolean specifying whether the secret must be supplied.
## `on.workflow_dispatch.inputs`
{% data reusables.github-actions.workflow-dispatch-inputs %}
{% data reusables.actions.workflow-dispatch-inputs %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## `permissions`
@@ -318,7 +318,7 @@ A unique identifier for the step. You can use the `id` to reference the step in
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
@@ -759,7 +759,7 @@ strategy:
## `jobs.<job_id>.container`
{% data reusables.github-actions.docker-container-os-support %}
{% data reusables.actions.docker-container-os-support %}
{% data reusables.actions.jobs.section-running-jobs-in-a-container %}
@@ -789,7 +789,7 @@ strategy:
## `jobs.<job_id>.services`
{% data reusables.github-actions.docker-container-os-support %}
{% data reusables.actions.docker-container-os-support %}
Used to host service containers for a job in a workflow. Service containers are useful for creating databases or cache services like Redis. The runner automatically creates a Docker network and manages the life cycle of the service containers.

2
content/admin/configuration/configuring-your-enterprise/restricting-network-traffic-to-your-enterprise.md
View File

@@ -70,4 +70,4 @@ For instance-level restrictions using Azure NSGs, contact {% data variables.cont
## Using {% data variables.product.prodname_actions %} with an IP allow list
{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
{% data reusables.actions.ip-allow-list-self-hosted-runners %}

2
content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
View File

@@ -111,7 +111,7 @@ You must configure external blob storage for these artifacts. Decide which suppo
{% ifversion ghec or ghes %}
{% data reusables.github-actions.artifact-log-retention-statement %}
{% data reusables.actions.artifact-log-retention-statement %}
{% endif %}

14
content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-github-actions-in-your-enterprise.md
View File

@@ -71,7 +71,7 @@ You can choose to disable {% data variables.product.prodname_actions %} for all
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
{% data reusables.actions.change-retention-period-for-artifacts-logs %}
{% endif %}
@@ -88,7 +88,7 @@ You can enforce policies to control how {% data variables.product.prodname_actio
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.github-actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
@@ -98,16 +98,16 @@ You can enforce policies to control how {% data variables.product.prodname_actio
### Enforcing a policy for fork pull requests in private repositories
{% data reusables.github-actions.private-repository-forks-overview %}
{% data reusables.actions.private-repository-forks-overview %}
If a policy is enabled for an enterprise, the policy can be selectively disabled in individual organizations or repositories. If a policy is disabled for an enterprise, individual organizations or repositories cannot enable it.
{% data reusables.github-actions.private-repository-forks-options %}
{% data reusables.actions.private-repository-forks-options %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
{% data reusables.enterprise-accounts.actions-tab %}
{% data reusables.github-actions.private-repository-forks-configure %}
{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
@@ -115,11 +115,11 @@ If a policy is enabled for an enterprise, the policy can be selectively disabled
## Enforcing a policy for workflow permissions in your enterprise
{% data reusables.github-actions.workflow-permissions-intro %}
{% data reusables.actions.workflow-permissions-intro %}
You can set the default permissions for the `GITHUB_TOKEN` in the settings for your enterprise, organizations, or repositories. If you choose the restricted option as the default in your enterprise settings, this prevents the more permissive setting being chosen in the organization or repository settings.
{% data reusables.github-actions.workflow-permissions-modifying %}
{% data reusables.actions.workflow-permissions-modifying %}
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}

2
content/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise.md
View File

@@ -119,7 +119,7 @@ You can also configure allowed IP addresses for an individual organization. For
### Using {% data variables.product.prodname_actions %} with an IP allow list
{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
{% data reusables.actions.ip-allow-list-self-hosted-runners %}
{% endif %}

6
content/billing/managing-billing-for-github-actions/about-billing-for-github-actions.md
View File

@@ -15,9 +15,9 @@ shortTitle: Billing for GitHub Actions
---
## About billing for {% data variables.product.prodname_actions %}
{% data reusables.github-actions.actions-billing %}
{% data reusables.actions.actions-billing %}
{% data reusables.github-actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
{% data reusables.actions.actions-spending-limit-brief %} For more information, see "[About spending limits](#about-spending-limits)."
{% ifversion ghec %}
If you purchased {% data variables.product.prodname_enterprise %} through a Microsoft Enterprise Agreement, you can connect your Azure Subscription ID to your enterprise account to enable and pay for {% data variables.product.prodname_actions %} usage beyond the amounts including with your account. For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
@@ -98,7 +98,7 @@ Your {% data variables.product.prodname_actions %} usage shares your account's e
## About spending limits
{% data reusables.github-actions.actions-spending-limit-detailed %}
{% data reusables.actions.actions-spending-limit-detailed %}
For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions)."

4
content/billing/managing-billing-for-github-actions/managing-your-spending-limit-for-github-actions.md
View File

@@ -18,9 +18,9 @@ shortTitle: Spending limits for Actions
---
## About spending limits for {% data variables.product.prodname_actions %}
{% data reusables.github-actions.actions-billing %}
{% data reusables.actions.actions-billing %}
{% data reusables.github-actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-packages-set-spending-limit %} For more information about pricing for {% data variables.product.prodname_actions %} usage, see "[About billing for {% data variables.product.prodname_actions %}](/billing/managing-billing-for-github-actions/about-billing-for-github-actions)."

2
content/billing/managing-billing-for-github-actions/viewing-your-github-actions-usage.md
View File

@@ -42,7 +42,7 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
{% note %}
**Note:** Billing details for enterprise accounts don't summarize the usage minutes for each operating system. {% data reusables.github-actions.enterprise-billing-details %}
**Note:** Billing details for enterprise accounts don't summarize the usage minutes for each operating system. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}

2
content/billing/managing-billing-for-github-packages/viewing-your-github-packages-usage.md
View File

@@ -41,7 +41,7 @@ Enterprise owners and billing managers can view {% data variables.product.prodna
{% note %}
**Note:** Billing details for enterprise accounts only summarize the storage data usage per organization. {% data reusables.github-actions.enterprise-billing-details %}
**Note:** Billing details for enterprise accounts only summarize the storage data usage per organization. {% data reusables.actions.enterprise-billing-details %}
{% endnote %}

8
content/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-encrypted-secrets-for-dependabot.md
View File

@@ -44,11 +44,11 @@ The name of a {% data variables.product.prodname_dependabot %} secret:
## Adding a repository secret for {% data variables.product.prodname_dependabot %}
{% data reusables.github-actions.permissions-statement-secrets-repository %}
{% data reusables.actions.permissions-statement-secrets-repository %}
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Click **New repository secret**.
1. Type a name for your secret in the **Name** input box.
@@ -63,11 +63,11 @@ The name of a {% data variables.product.prodname_dependabot %} secret:
When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
{% data reusables.github-actions.permissions-statement-secrets-organization %}
{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
{% data reusables.dependabot.dependabot-secrets-button %}
1. Click **New organization secret**.
1. Type a name for your secret in the **Name** input box.

4
content/codespaces/managing-codespaces-for-your-organization/managing-encrypted-secrets-for-your-repository-and-organization-for-codespaces.md
View File

@@ -51,7 +51,7 @@ To create secrets for an organization repository, you must have administrator ac
When creating a secret in an organization, you can use a policy to limit which repositories can access that secret. For example, you can grant access to all repositories, or limit access to only private repositories or a specified list of repositories.
{% data reusables.github-actions.permissions-statement-secrets-organization %}
{% data reusables.actions.permissions-statement-secrets-organization %}
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
@@ -69,7 +69,7 @@ You can check which access policies are applied to a secret in your organization
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.github-actions.sidebar-secret %}
{% data reusables.actions.sidebar-secret %}
1. The list of secrets includes any configured permissions and policies. For example:
![Secrets list](/assets/images/help/settings/actions-org-secrets-list.png)
1. For more details on the configured permissions for each secret, click **Update**.

2
content/get-started/learning-about-github/githubs-products.md
View File

@@ -88,7 +88,7 @@ In addition to the features available with {% data variables.product.prodname_fr
{% data variables.product.company_short %} bills for {% data variables.product.prodname_team %} on a per-user basis. For more information, see "[About per-user pricing]({% ifversion not fpt %}/free-pro-team@latest{% endif %}/billing/managing-billing-for-your-github-account/about-per-user-pricing){% ifversion fpt %}."{% else %}" in the Free, Pro, & Team documentation.{% endif %}
{% data reusables.github-actions.actions-billing %}
{% data reusables.actions.actions-billing %}
## {% data variables.product.prodname_enterprise %}

2
content/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md
View File

@@ -84,4 +84,4 @@ For more information about how to create an allow list for a {% data variables.p
## Using {% data variables.product.prodname_actions %} with an IP allow list
{% data reusables.github-actions.ip-allow-list-self-hosted-runners %}
{% data reusables.actions.ip-allow-list-self-hosted-runners %}

2
content/organizations/managing-organization-settings/configuring-the-retention-period-for-github-actions-artifacts-and-logs-in-your-organization.md
View File

@@ -21,4 +21,4 @@ shortTitle: Configure retention period
{% data reusables.organizations.navigate-to-org %}
{% data reusables.organizations.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
{% data reusables.actions.change-retention-period-for-artifacts-logs %}

18
content/organizations/managing-organization-settings/disabling-or-limiting-github-actions-for-your-organization.md
View File

@@ -19,11 +19,11 @@ shortTitle: Disable or limit actions
## About {% data variables.product.prodname_actions %} permissions for your organization
{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
{% data reusables.actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.github-actions.disabled-actions-description %}
You can enable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for all repositories in your organization. {% data reusables.actions.disabled-actions-description %}
Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
Alternatively, you can enable {% data variables.product.prodname_actions %} for all repositories in your organization but limit the actions a workflow can run. {% data reusables.actions.enabled-local-github-actions %}
## Managing {% data variables.product.prodname_actions %} permissions for your organization
@@ -69,7 +69,7 @@ You can configure this behavior for an organization using the procedure below. M
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
{% data reusables.github-actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
@@ -77,28 +77,28 @@ You can configure this behavior for an organization using the procedure below. M
{% ifversion fpt or ghes or ghec %}
## Enabling workflows for private repository forks
{% data reusables.github-actions.private-repository-forks-overview %}
{% data reusables.actions.private-repository-forks-overview %}
{% ifversion ghec or ghae or ghes %}If a policy is disabled for an enterprise, it cannot be enabled for organizations.{% endif %} If a policy is disabled for an organization, it cannot be enabled for repositories. If an organization enables a policy, the policy can be disabled for individual repositories.
{% data reusables.github-actions.private-repository-forks-options %}
{% data reusables.actions.private-repository-forks-options %}
### Configuring the private fork policy for an organization
{% data reusables.profile.access_org %}
{% data reusables.profile.org_settings %}
{% data reusables.organizations.settings-sidebar-actions %}
{% data reusables.github-actions.private-repository-forks-configure %}
{% data reusables.actions.private-repository-forks-configure %}
{% endif %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Setting the permissions of the `GITHUB_TOKEN` for your organization
{% data reusables.github-actions.workflow-permissions-intro %}
{% data reusables.actions.workflow-permissions-intro %}
You can set the default permissions for the `GITHUB_TOKEN` in the settings for your organization or your repositories. If you choose the restricted option as the default in your organization settings, the same option is auto-selected in the settings for repositories within your organization, and the permissive option is disabled. If your organization belongs to a {% data variables.product.prodname_enterprise %} account and the more restricted default has been selected in the enterprise settings, you won't be able to choose the more permissive default in your organization settings.
{% data reusables.github-actions.workflow-permissions-modifying %}
{% data reusables.actions.workflow-permissions-modifying %}
### Configuring the default `GITHUB_TOKEN` permissions

20
content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
View File

@@ -24,11 +24,11 @@ shortTitle: Manage GitHub Actions settings
## About {% data variables.product.prodname_actions %} permissions for your repository
{% data reusables.github-actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
{% data reusables.actions.disabling-github-actions %} For more information about {% data variables.product.prodname_actions %}, see "[About {% data variables.product.prodname_actions %}](/actions/getting-started-with-github-actions/about-github-actions)."
You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.github-actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.github-actions.disabled-actions-description %}
You can enable {% data variables.product.prodname_actions %} for your repository. {% data reusables.actions.enabled-actions-description %} You can disable {% data variables.product.prodname_actions %} for your repository altogether. {% data reusables.actions.disabled-actions-description %}
Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.github-actions.enabled-local-github-actions %}
Alternatively, you can enable {% data variables.product.prodname_actions %} in your repository but limit the actions a workflow can run. {% data reusables.actions.enabled-local-github-actions %}
## Managing {% data variables.product.prodname_actions %} permissions for your repository
@@ -78,34 +78,34 @@ You can configure this behavior for a repository using the procedure below. Modi
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
{% data reusables.github-actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflows-from-public-fork-setting %}
{% data reusables.actions.workflow-run-approve-link %}
{% endif %}
## Enabling workflows for private repository forks
{% data reusables.github-actions.private-repository-forks-overview %}
{% data reusables.actions.private-repository-forks-overview %}
If a policy is disabled for an {% ifversion ghec or ghae or ghes %}enterprise or{% endif %} organization, it cannot be enabled for a repository.
{% data reusables.github-actions.private-repository-forks-options %}
{% data reusables.actions.private-repository-forks-options %}
### Configuring the private fork policy for a repository
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
{% data reusables.github-actions.private-repository-forks-configure %}
{% data reusables.actions.private-repository-forks-configure %}
{% ifversion fpt or ghes > 3.1 or ghae or ghec %}
## Setting the permissions of the `GITHUB_TOKEN` for your repository
{% data reusables.github-actions.workflow-permissions-intro %}
{% data reusables.actions.workflow-permissions-intro %}
The default permissions can also be configured in the organization settings. If the more restricted default has been selected in the organization settings, the same option is auto-selected in your repository settings and the permissive option is disabled.
{% data reusables.github-actions.workflow-permissions-modifying %}
{% data reusables.actions.workflow-permissions-modifying %}
### Configuring the default `GITHUB_TOKEN` permissions
@@ -152,4 +152,4 @@ You can also define a custom retention period for a specific artifact created by
{% data reusables.repositories.navigate-to-repo %}
{% data reusables.repositories.sidebar-settings %}
{% data reusables.repositories.settings-sidebar-actions %}
{% data reusables.github-actions.change-retention-period-for-artifacts-logs %}
{% data reusables.actions.change-retention-period-for-artifacts-logs %}

0
data/reusables/github-actions/actions-activity-types.md → data/reusables/actions/actions-activity-types.md
View File

0
data/reusables/github-actions/actions-billing.md → data/reusables/actions/actions-billing.md
View File

0
data/reusables/github-actions/actions-do-not-trigger-workflows.md → data/reusables/actions/actions-do-not-trigger-workflows.md
View File

0
data/reusables/github-actions/actions-filters.md → data/reusables/actions/actions-filters.md
View File

0
data/reusables/github-actions/actions-multiple-types.md → data/reusables/actions/actions-multiple-types.md
View File

19
data/reusables/actions/actions-on-examples.md Normal file
View File

@@ -0,0 +1,19 @@
### Using a single event
{% data reusables.actions.on-single-example %}
### Using multiple events
{% data reusables.actions.on-multiple-example %}
### Using activity types
{% data reusables.actions.actions-activity-types %}
### Using filters
{% data reusables.actions.actions-filters %}
### Using activity types and filters with multiple events
{% data reusables.actions.actions-multiple-types %}

0
data/reusables/github-actions/actions-spending-limit-brief.md → data/reusables/actions/actions-spending-limit-brief.md
View File

2
data/reusables/github-actions/actions-spending-limit-detailed.md → data/reusables/actions/actions-spending-limit-detailed.md
View File

@@ -1,3 +1,3 @@
{% data reusables.github-actions.actions-spending-limit-brief %}
{% data reusables.actions.actions-spending-limit-brief %}
If you have an unlimited spending limit or a spending limit set higher than $0 USD, you will be billed for any additional minutes or storage beyond the included amounts in your account, also called overages. {% data variables.product.prodname_dotcom %} charges usage to the account that owns the repository where a workflow is run. Any coupons on your account do not apply to {% data variables.product.prodname_actions %} overages.

0
data/reusables/github-actions/actions-unused-labels.md → data/reusables/actions/actions-unused-labels.md
View File

0
data/reusables/github-actions/artifact-log-retention-statement.md → data/reusables/actions/artifact-log-retention-statement.md
View File

0
data/reusables/github-actions/branch-paths-filter.md → data/reusables/actions/branch-paths-filter.md
View File

0
data/reusables/github-actions/branch-requirement.md → data/reusables/actions/branch-requirement.md
View File

0
data/reusables/github-actions/change-retention-period-for-artifacts-logs.md → data/reusables/actions/change-retention-period-for-artifacts-logs.md
View File

0
data/reusables/github-actions/contacting-support.md → data/reusables/actions/contacting-support.md
View File

0
data/reusables/github-actions/container-jobs-intro.md → data/reusables/actions/container-jobs-intro.md
View File

0
data/reusables/github-actions/context-injection-warning.md → data/reusables/actions/context-injection-warning.md
View File

0
data/reusables/github-actions/copy-workflow-file.md → data/reusables/actions/copy-workflow-file.md
View File

0
data/reusables/github-actions/defaults-override.md → data/reusables/actions/defaults-override.md
View File

0
data/reusables/github-actions/disabled-actions-description.md → data/reusables/actions/disabled-actions-description.md
View File

0
data/reusables/github-actions/disabling-github-actions.md → data/reusables/actions/disabling-github-actions.md
View File

0
data/reusables/github-actions/docker-container-os-support.md → data/reusables/actions/docker-container-os-support.md
View File

0
data/reusables/github-actions/dockerfile-guidelines.md → data/reusables/actions/dockerfile-guidelines.md
View File

0
data/reusables/github-actions/enabled-actions-description.md → data/reusables/actions/enabled-actions-description.md
View File

0
data/reusables/github-actions/enabled-local-github-actions.md → data/reusables/actions/enabled-local-github-actions.md
View File

0
data/reusables/github-actions/enterprise-billing-details.md → data/reusables/actions/enterprise-billing-details.md
View File

0
data/reusables/github-actions/example-github-runner.md → data/reusables/actions/example-github-runner.md
View File

0
data/reusables/github-actions/expression-syntax-if.md → data/reusables/actions/expression-syntax-if.md
View File

0
data/reusables/github-actions/forked-write-permission.md → data/reusables/actions/forked-write-permission.md
View File

0
data/reusables/github-actions/github-context-warning.md → data/reusables/actions/github-context-warning.md
View File

0
data/reusables/github-actions/github-hosted-runners-check-concurrency.md → data/reusables/actions/github-hosted-runners-check-concurrency.md
View File

0
data/reusables/github-actions/github-hosted-runners-navigate-to-repo-org-enterprise.md → data/reusables/actions/github-hosted-runners-navigate-to-repo-org-enterprise.md
View File

0
data/reusables/github-actions/github-hosted-runners-table-entry.md → data/reusables/actions/github-hosted-runners-table-entry.md
View File

0
data/reusables/github-actions/github-token-available-permissions.md → data/reusables/actions/github-token-available-permissions.md
View File

0
data/reusables/github-actions/github-token-permissions.md → data/reusables/actions/github-token-permissions.md
View File

0
data/reusables/github-actions/github_token-input-example.md → data/reusables/actions/github_token-input-example.md
View File

0
data/reusables/github-actions/gradle-workflow-steps.md → data/reusables/actions/gradle-workflow-steps.md
View File

0
data/reusables/github-actions/hosted-runner-configure-runner-group-access.md → data/reusables/actions/hosted-runner-configure-runner-group-access.md
View File

0
data/reusables/github-actions/hosted-runner-labels-view-assigned-labels.md → data/reusables/actions/hosted-runner-labels-view-assigned-labels.md
View File

0
data/reusables/github-actions/hosted-runner-list-group.md → data/reusables/actions/hosted-runner-list-group.md
View File

Some files were not shown because too many files have changed in this diff Show More