Configuration / Suppressions

Suppressions

Suppressions drop candidate findings before the hearing. They are cheaper than a high threshold, because a suppressed finding is never heard at all.

Categories

Category	Covers
style	Formatting, ordering, and structural preference with no behavioural difference.
naming	Identifier naming and casing.
typing	Type-narrowing and annotation suggestions your type checker does not require.
test_coverage	Requests for additional tests on changed code.
docs	Missing or stale comments and docstrings.
performance	Optimisation suggestions with no correctness impact.

suppress:
  - style          # the formatter owns this
  - test_coverage  # our CI gate owns this

When to suppress instead of raising the threshold

Raise the threshold when the panel is posting findings that are wrong. Suppress when it is posting findings that are correct but not yours to act on — a formatter, a linter or a coverage gate already owns them.

Suppressing a single finding

Reply @dicast dismiss to a comment. That marks the pattern as unhelpful for this repository and lowers its prior in future hearings — see commands. Unlike a category suppression, it is specific and it is recorded.

Note

Suppressed findings do not appear in the struck record, because they were never heard. If you want the record, raise the threshold instead.