Skip to content

fix(review): fail closed on incomplete coverage #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pierrick-fonquerne merged 2 commits into from
Aug 12, 2026
Merged

fix(review): fail closed on incomplete coverage #35

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
088cdf2
fix(review): fail closed on incomplete coverage
Aug 12, 2026
4a55945
fix(review): remove stale inline results
Aug 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,11 @@ Oversized hunks receive recalculated old/new coordinates in every fragment,
and each bounded batch is synthesised independently before reports are joined.
The collected file count is also checked against the pull request metadata so
GitHub's 3,000-file endpoint limit cannot look like complete coverage.
The deterministic team verdict is `INCOMPLETE` whenever any input gap remains
or the verification cap leaves findings unchecked; a confirmed critical still
takes precedence as `NEEDS_WORK`. Re-running a mode on the same head commit
updates its global and inline bot comments instead of publishing duplicates,
and removes inline results that are no longer confirmed by that mode.

### Calling the reusable workflow

Expand Down
Loading