feat: refine review label workflow and support comment triggers.#1
Merged
Conversation
…els. Signed-off-by: Li Guan <guanli.oerv@isrc.iscas.ac.cn>
Signed-off-by: Li Guan <guanli.oerv@isrc.iscas.ac.cn>
…Review label exists. Signed-off-by: Li Guan <guanli.oerv@isrc.iscas.ac.cn>
…nts configuration Signed-off-by: Li Guan <guanli.oerv@isrc.iscas.ac.cn>
Signed-off-by: Li Guan <guanli.oerv@isrc.iscas.ac.cn>
misaka00251
approved these changes
May 21, 2026
misaka00251
added
Community: Student contribution
misaka00251
added
Workflow: Complete
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
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.
Summary
This PR refines our automated PR labeling workflow. It introduces comment-triggered label updates, fixes a few edge cases in label transitions, and updates the setup docs.
What changed
Impact
The previous logic caused some clunky label transitions and missed edge cases. These changes make the bot's behavior much more predictable. We also documented the setup requirements to save future maintainers from guessing which permissions the App needs.