Repository navigation
CI: assign-milestone sets a pull request's milestone (pull-requests: write) - #260
Merged
Merged
Conversation
The workflow from #252 failed on the merges of #252 and #256 with 403 Resource not accessible by integration when it set the pull request's milestone; issues: write covers issues only. The workflow still checks out no pull request code (pull_request_target), so the wider token stays safe. Closes #259 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Closes #259
The
Assign release milestoneworkflow (#252) failed with403 Resource not accessible by integrationwhen it set the milestone of a merged pull request;issues: writecovers issues only, so the job needspull-requests: write. It checks out no pull request code (it runs onpull_request_targetand calls the API only), so the wider token stays safe. Checked with actionlint and pre-commit; the first merge after this one shows the PR side working.🤖 Generated with Claude Code