jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-22 03:16:52 -05:00
Code Issues Projects Releases Wiki Activity

Actions: bug fix hour PR (#39602)

Browse Source 
Co-authored-by: github-actions <github-actions@github.com>
This commit is contained in:
hubwriter
2023-07-25 06:55:06 +01:00
committed by GitHub
parent c4b1ee173b
commit c5ad5e6868
4 changed files with 10 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
assets/images/help/actions/creating-selfhosted-runner.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 42 KiB

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

@@ -18,7 +18,7 @@ shortTitle: Automatic token authentication
## About the `GITHUB_TOKEN` secret
At the start of each workflow run, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in a workflow run.
At the start of each workflow job, {% data variables.product.prodname_dotcom %} automatically creates a unique `GITHUB_TOKEN` secret to use in your workflow. You can use the `GITHUB_TOKEN` to authenticate in the workflow job.
When you enable {% data variables.product.prodname_actions %}, {% data variables.product.prodname_dotcom %} installs a {% data variables.product.prodname_github_app %} on your repository. The `GITHUB_TOKEN` secret is a {% data variables.product.prodname_github_app %} installation access token. You can use the installation access token to authenticate on behalf of the {% data variables.product.prodname_github_app %} installed on your repository. The token's permissions are limited to the repository that contains your workflow. For more information, see "[Permissions for the `GITHUB_TOKEN`](#permissions-for-the-github_token)."

6
content/admin/github-actions/managing-access-to-actions-from-githubcom/manually-syncing-actions-from-githubcom.md
View File

@@ -68,6 +68,12 @@ This example demonstrates using the `actions-sync` tool to sync an individual ac
1. Download and extract the latest [`actions-sync` release](https://github.com/actions/actions-sync/releases) for your machine's operating system.
1. Create a directory to store cache files for the tool.
1. In your terminal, change to the `bin` directory within the release directory you just extracted. For example:
```shell
cd PATH/TO/gh_DATETIME_OS_ARCHITECTURE/bin
```
1. Run the `actions-sync sync` command:
```shell

3
data/reusables/actions/self-hosted-runner-configure.md
View File

@@ -1,4 +1,7 @@
1. Select the operating system image and architecture of your self-hosted runner machine.
![Screenshot of the choice of operating system and architecture. These options are highlighted with a dark orange outline.](/assets/images/help/actions/creating-selfhosted-runner.png)
1. You will see instructions showing you how to download the runner application and install it on your self-hosted runner machine.
Open a shell on your self-hosted runner machine and run each shell command in the order shown.