ci: give explicit PR permissions to GitHub token #141
Merged
Conversation
This file contains 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
When dependabot triggers a PR the GITHUB_TOKEN is read-only and must explicitly be given write permissions.[1] This is a side effect of upgrading to the v5 create-pull-request-action. Explicitly set these in the workflow to avoid it failing on commits by dependabot, but also to more clearly define the workflow's expected permissions. [1] peter-evans/create-pull-request#1873
3v1n0
approved these changes
Dec 12, 2023
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.
When dependabot triggers a PR the
GITHUB_TOKENis read-only and must explicitly be given write permissions. This is a side effect of upgrading to the v5 create-pull-request-action.Explicitly set these in the workflow to avoid it failing on commits by dependabot, but also to more clearly define the workflow's expected permissions.