Repository navigation
Comment for Registrator with the workflow's own token - #48
Merged
Merged
Conversation
Registrator acts on comments from github-actions[bot], as well as from collaborators and members of the repository's organization, so the register job comments with GITHUB_TOKEN and needs no machine user. The job takes its caller's permissions, contents: write, since a called job that asks for more than its caller grants doesn't start; so callers that pass REGISTRATOR_TOKEN with contents: read still work, and it comments instead where it's given. Where GitHub refuses the comment, the error gives GitHub's message and what the token needs, and the job summary the comment to make by hand.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Registrator acts on comments from github-actions[bot], as well as from collaborators and members of the repository's organization, so the register job comments with GITHUB_TOKEN and needs no machine user. The job takes its caller's permissions, contents: write, since a called job that asks for more than its caller grants doesn't start; so callers that pass REGISTRATOR_TOKEN with contents: read still work, and it comments instead where it's given.
Where GitHub refuses the comment, the error gives GitHub's message and what the token needs, and the job summary the comment to make by hand.