Remove assigning and adding reviewer to merge-back PR #3249
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
infomiho
approved these changes
Oct 13, 2025
|
Reported the bug at the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When pushing to
release, in the merge-back automation, we check if a PR already exists. If so, the person who pushed isThis PR removes action (2). This is because the
gh pr editcommand needs access toorganization.read, and GitHub actions can't request access to this scope (failed run log).Note: it is weird that the CLI requests this scope, as the underlying APIs do not need it (only
pull_request.write-- 1, 2). My guess is that the CLI is first checking if the string we pass it is a team name or a user name to do some intelligent handling around that, and that's why it needs theorg.readscope for.