feat(judge): add --summary to print the verdict without the per-finding list - #24
Merged
Conversation
…ng list gavel judge always dumps every finding file-by-file — 213 lines on a 146-finding project — even with --quick, which only narrows *which checks run*, not the output. That buries the verdict and the new-vs-baseline delta, and floods CI logs. --summary keeps the verdict, the delta, and the per-dimension rulings but omits the per-finding list and the coverage-by-directory tree: 213 lines collapse to 13. --quick controls analysis scope; --summary controls output verbosity — orthogonal, composable (`gavel judge --quick --summary`).
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Gavel verdict
|
JorgeOlmosDev
added a commit
that referenced
this pull request
Jul 13, 2026
…ng list (#24) gavel judge always dumps every finding file-by-file — 213 lines on a 146-finding project — even with --quick, which only narrows *which checks run*, not the output. That buries the verdict and the new-vs-baseline delta, and floods CI logs. --summary keeps the verdict, the delta, and the per-dimension rulings but omits the per-finding list and the coverage-by-directory tree: 213 lines collapse to 13. --quick controls analysis scope; --summary controls output verbosity — orthogonal, composable (`gavel judge --quick --summary`).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
gavel judgealways dumps every finding file-by-file — 213 lines on a 146-finding project — then the verdict.--quickdoesn't help: it narrows which checks run (skips coverage + architecture), not the output, so the finding list is just as long. The result buries the verdict and the new-vs-baseline delta, and floods CI logs.(
--quick= analysis scope · output verbosity = a different axis entirely.)Fix
--summarykeeps the verdict, the delta (N new · M fixed · K existing), and the per-dimension rulings, but omits the per-finding list and the coverage-by-directory tree.--quickand--summaryare orthogonal and compose. Verdict, exit code, and JSON output (--json) are all unchanged — this only gates the human finding-list render.Tests (TDD)
TestEmitResults_SummaryOmitsFindingList: default output lists findings;--summaryomits them but still shows the verdict.clispec/v1/clispec.yaml;flags.gen.goregenerated (make clispec-gen); clispec integration tests pass.