Skip to content

Commit 099d0bd

Browse files
author
Premiermoney
authored
Merge branch 'github:main' into patch-2
2 parents 7d27849 + 5559346 commit 099d0bd

202 files changed

Lines changed: 3002 additions & 61182 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
32.2 KB
Loading
53.8 KB
Loading
17.4 KB
Loading
12.2 KB
Loading
-72.4 KB
Loading

content/actions/concepts/security/github_token.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,11 @@ The token is also available in the `github.token` context. For more information,
2929

3030
{% data reusables.actions.actions-do-not-trigger-workflows %}
3131

32+
{% ifversion actions-github-token-pull-request-approval %}
33+
> [!NOTE]
34+
> If you need workflow runs from workflow-created pull requests to execute without requiring approval, use a {% data variables.product.prodname_github_app %} installation access token or a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` when creating or updating the pull request.
35+
{% endif %}
36+
3237
{% data reusables.actions.actions-do-not-trigger-pages-rebuilds %}
3338

3439
## Next steps

content/actions/how-tos/create-and-publish-actions/publish-in-github-marketplace.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,6 @@ Actions are published to {% data variables.product.prodname_marketplace %} immed
3232
* The action must be in a public repository.
3333
* Each repository must contain a single action metadata file (`action.yml` or `action.yaml`) at the root.
3434
* Repositories may include other actions metadata files in sub-folders, but they will not be automatically listed in the marketplace.
35-
* Each repository must _not_ contain any workflow files.
3635
* The `name` in the action's metadata file must be unique.
3736
* The `name` cannot match an existing action name published on {% data variables.product.prodname_marketplace %}.
3837
* The `name` cannot match a user or organization on {% data variables.product.prodname_dotcom %}, unless the user or organization owner is publishing the action. For example, only the {% data variables.product.prodname_dotcom %} organization can publish an action named `github`.

content/actions/how-tos/manage-runners/use-actions-runner-controller/deploy-runner-scale-sets.md

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -624,9 +624,6 @@ containerMode:
624624
type: "kubernetes-novolume"
625625
```
626626

627-
>[!NOTE]
628-
>When using `kubernetes-novolume` mode, the container must run as `root` to support lifecycle hook operations.
629-
630627
#### Troubleshooting Kubernetes mode
631628

632629
When Kubernetes mode is enabled, workflows that are not configured with a container job will fail with an error similar to:

content/actions/how-tos/manage-workflow-runs/approve-runs-from-forks.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Approving workflow runs from forks
3-
intro: You can manually approve workflow runs that have been triggered by a contributor's pull request.
3+
intro: You can manually approve workflow runs triggered by a contributor's pull request.
44
versions:
55
fpt: '*'
66
ghec: '*'

content/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To learn more about workflows and triggering workflows, see [AUTOTITLE](/actions
2525

2626
{% data reusables.actions.actions-do-not-trigger-workflows %} For more information, see [AUTOTITLE](/actions/security-guides/automatic-token-authentication).
2727

28-
If you do want to trigger a workflow from within a workflow run, you can use a {% data variables.product.prodname_github_app %} installation access token or a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` to trigger events that require a token.
28+
If you do want to trigger a workflow from within a workflow run, you can use a {% data variables.product.prodname_github_app %} installation access token or a {% data variables.product.pat_generic %} instead of `GITHUB_TOKEN` to trigger events that require a token.{% ifversion actions-github-token-pull-request-approval %} Using one of these alternatives also lets `pull_request` workflows run automatically (without the approval prompt described above) when the pull request is created or updated by automation.{% endif %}
2929

3030
If you use a {% data variables.product.prodname_github_app %}, you'll need to create a {% data variables.product.prodname_github_app %} and store the app ID and private key as secrets. For more information, see [AUTOTITLE](/apps/creating-github-apps/guides/making-authenticated-api-requests-with-a-github-app-in-a-github-actions-workflow). If you use a {% data variables.product.pat_generic %}, you'll need to create a {% data variables.product.pat_generic %} and store it as a secret. For more information about creating a {% data variables.product.pat_generic %}, see [AUTOTITLE](/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token). For more information about storing secrets, see [AUTOTITLE](/actions/security-guides/using-secrets-in-github-actions).
3131

0 commit comments

Comments
 (0)