-
Notifications
You must be signed in to change notification settings - Fork 1
review: hold for a human instead of approving when core lenses produced no output #338
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.
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
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,19 @@ | ||
| --- | ||
| "review": minor | ||
| --- | ||
|
|
||
| A run whose core review pass (`correctness-reviewer` or `skill-auditor`) | ||
| produced no output no longer auto-approves: the plan CLI now feeds the | ||
| dispatcher's real `skippedDimensions` into `computeVerdict`, whose | ||
| HOLD_FOR_HUMAN gate was previously unreachable (the dimensions were hardcoded | ||
| "assessed"). A hold submits no review event; the plan's body posts as one | ||
| standalone PR comment explaining the hold and how to get unstuck, the | ||
| conformance gate blocks any other shape (a queued review event, inline | ||
| comments, thread resolutions, or a withheld hold comment), and the cache | ||
| writer leaves the prior fingerprints standing so the next run reviews in | ||
| full (it drops only `risksPatternsKey`, because posting the hold comment | ||
| collapses the standing guidance comment). Blocking findings still win: with | ||
| a validated blocking claim the verdict stays REQUEST_CHANGES and the dead | ||
| lens is disclosed in a note line. The production shape this closes: | ||
| Khan/actions#328's re-run, where every core lens died on an API auth error | ||
| and the bot still submitted "Approved" over seven "not assessed" notes. |
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.