Fix reusable workflow pin to match granted permissions#157
Merged
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
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
pull requestsandissuesworkflows call the sharedlaravel/.githubreusable workflows pinned todd86ce0.At that commit the reusable workflows declare
permissions: contents: read(andpull-requests: writeforissues.yml), but the callers here only grantpull-requests: write/issues: write. A reusable workflow cannot request a permission the caller didn't grant, so every run fails at startup (startup_failure).This bumps the pin to the current
laravel/.githubmain SHAc265c45, which was trimmed to require only the scopes the callers already grant — resolving the failure.