fix(ci): grant issues:write to remove_wip_label workflow#25339
Merged
Conversation
The github.rest.issues.removeLabel call (DELETE /repos/{owner}/{repo}/issues/{issue_number}/labels/{name})
requires the issues:write permission per the GitHub REST API. The workflow
only declared pull-requests:write, so the call returned 403 the first time
all preconditions actually held simultaneously (MEMBER reviewer + label
present + approval).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
thomasqueirozb
approved these changes
May 1, 2026
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Grant
issues: writeto theRemove Work In Progress Labelworkflow so theremoveLabelREST call succeeds.The
DELETE /repos/{owner}/{repo}/issues/{issue_number}/labels/{name}endpoint requiresissues: writeper the GitHub REST API docs.This was first observed when run 25135003048 attempted the call against #25057 — the first time all three preconditions held simultaneously: MEMBER reviewer, "work in progress" label present, and an approving review. Prior runs all bailed out earlier (CONTRIBUTOR reviewer or label not present).
How did you test this PR?
Tested in ci-sandbox:
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References