Repository navigation
ci(automerge): grant issues: write so an auto-merged PR closes its issue - #38
Merged
Merged
Conversation
PR #34 carried "Closes #33" and was auto-merged by the automerge workflow, but issue #33 stayed open. The workflow's permissions block grants only contents and pull-requests, so the issues scope is none for the token that performs the merge. A person-merged PR (#35) closed its issue normally. Add issues: write. Co-Authored-By: Claude Sonnet 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.
Follow-up to #37. Adds
issues: writeto the automerge workflow's permissions.Why
PR #34 carried
Closes #33and merged through the automerge workflow, but issue #33 stayed open (its linked references were correct,closingIssuesReferences = [33]). The workflow's explicitpermissions:block grants onlycontentsandpull-requests, so every other scope, includingissues, isnonefor the token that performs the merge. Issue #10 was closed normally by PR #35, which a person merged. That is consistent with the missing scope being the cause, but it is a hypothesis until a labeled bot PR with aClosesline merges under this change.Check after merge
Label the next bot-opened PR that has a
Closes #Nlineautomergeand confirm issue #N closes itself. If it does not, the cause is elsewhere and this line can be reverted.Notes
GITHUB_TOKENdoes not startpushworkflows onmain.🤖 Generated with Claude Code