Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The concurrency key only looks at the comment text. The job
if(lines 32–34) also requiresgithub.event.issue.pull_requestand an OWNER/MEMBER/COLLABORATORauthor_association. Because concurrency is applied before the jobif, an@claude reviewcomment from anyone without those roles still joins the sharedclaude-review-<N>group. That includes a fork PR author or any user on this public repo. Withcancel-in-progress: true, the comment cancels a running review, and its own run is then skipped. So the self-cancel bug is fixed, but anyone can still cancel a review just by commenting. Use the sameauthor_associationcheck in the concurrency condition, so only comments that would actually start a review share the group. For example:A smaller version of the same problem:
pull_requestreopened/ready_for_reviewevents on fork PRs still use the shared group, so they can cancel a maintainer-requested review even though their own job is skipped by thehead.repo.full_namecheck.