Update reference link re: GITHUB_TOKEN permissions for workflow runs triggered by events from forks #143
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…triggered by events from forks The personal access token used by the action to make the report comment must have write permissions. The action uses the automatically generated `GITHUB_TOKEN` token by default. When the action is used in a public repository, it is essential for the maintainer of the repository to understand how the permissions of that token work. For security reasons, the permissions of the token are downgraded to write when used in a workflow run triggered by an event that comes from a fork. This is the reason why another approach must be used to run the action's workflow in public repositories. The action documentation provides an explanation of this, but relies on the GitHub Actions documentation to explain the details of the token permissions downgrade system. Due to changes in the GitHub documentation, the linked page no longer contains that information. The link is hereby updated to point to the information in its new location in the GitHub Actions docs.
per1234
added
type: imperfection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The personal access token used by the action to make the report comment must have write permissions. The action uses the automatically generated
GITHUB_TOKENtoken by default.When the action is used in a public repository, it is essential for the maintainer of the repository to understand how the permissions of that token work. For security reasons, the permissions of the token are downgraded to write when used in a workflow run triggered by an event that comes from a fork. This is the reason why another approach must be used to run the action's workflow in public repositories.
The action documentation provides an explanation of this, but relies on the GitHub Actions documentation to explain the details of the token permissions downgrade system. Due to changes in the GitHub documentation, the linked page no longer contains that information. The link is hereby updated to point to the information in its new location in the GitHub Actions docs.