Pre-merge check failures should set review event to RequestChanges #7
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
crates/ar-review/src/mapping.rs:17-25only escalates the review event toRequestChangeswhen at least one finding has severity=Error. Pre-merge check failures (CHANGELOG missing, tests missing, no-new-todos triggered, repo-author custom natural-language checks failing) render in the review body but don't influence the event.That's a real gap — a missing CHANGELOG or missing tests is a stronger "don't merge yet" signal than most note-level findings, but the review still posts as event=Comment.
Proposed: any failed pre-merge check (built-in deterministic OR repo-author-supplied) bumps event to RequestChanges, regardless of finding severities. A single boolean in the mapping function.
Touches:
crates/ar-review/src/mapping.rsand probably the call site incrates/ar-orchestrator/src/dispatcher.rs(whichever assembles the final ReviewOutput → CreateReviewRequest).