Repository navigation
fix(github.issue.welcome): grant issue read permission for PR history - #43
Merged
Merged
Conversation
github-actions
Bot
added
💾 actions
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.
👋 Background
The PR welcome job fails with
403 Resource not accessible by integrationwhen looking up the author's contribution history. It callsissues.listForRepo, which requiresissues: readeven when checking pull requests; the caller currently grants onlypull-requests: write.🔗 Related Issues
⚙️ Description
issues: readto this repository's PR welcome job while retainingpull-requests: writefor comments.Validation: all 16 welcome tests passed; yamllint, jactionlint correctness checks, GitHub Actions/workflow schema validation, and
git diff --checkpassed.🚨 To Reviewers
Caller workflows must grant the permission; a reusable workflow cannot elevate the caller's token. The companion Terraform-template PR must also be deployed to update downstream callers. Rerunning the original failing workflow revision alone will not pick up the caller permission change.