chore: anchor Claude verdict marker filter to line-start#8835
Conversation
Workflow-level concurrency joins the group before job if: filters run, so claude[bot]'s own progress comments triggered new issue_comment runs that cancelled in-flight reviews. Move concurrency to the auto-review and review jobs so skipped jobs never enter the group.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
🔒 Claude reviewed this PR — sensitive paths modified ( |
|
Claude finished @aixaCode's task in 23s —— View job Review
Root-cause checkThis PR fixes a minor grammar/phrasing issue in documentation ( Diff summary
Blocking issuesNone. Non-blocking warningsNone. REVIEW_RESULT: PASS ✅ |
Substring match on REVIEW_RESULT: / DEPENDENCY_REVIEW: also catches review bodies that merely discuss the marker text, so cross-workflow verdicts were getting minimized as collateral. Require a real verdict value (PASS/FAIL/BLOCK/NEEDS_ATTENTION) on its own line.
Dismissed: latest Claude review no longer auto-approves this PR.
Summary
Follow-up to #8833. The dedupe filter matched
REVIEW_RESULT:/DEPENDENCY_REVIEW:anywhere in the body, so when one Claude review's verdict text discusses the other's marker (e.g. on workflow-meta PRs) the wrong comment got minimized.Tighten the filter to require an actual verdict value (
PASS/FAILfor code review;PASS/BLOCK/NEEDS_ATTENTIONfor dependency security) at the start of a line. Mentions inside prose or inline code no longer match.Also includes a tiny doc wording tweak in
docs/master-of-bots.mdfrom the earlier smoke test that surfaced this bug.Test plan