Skip to content

Fail CI when a new ruff finding exceeds today's baseline - #180

Merged
jmjava merged 1 commit into
mainfrom
ratchet/docgen-ruff-baseline
Oct 11, 2026
Merged

jmjava merged 1 commit into
mainfrom
ratchet/docgen-ruff-baseline

Conversation

@jmjava

@jmjava jmjava commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Summary

  • Freeze today's ruff findings (none, under the existing E4/E7/E9/F select) in config/ruff-baseline.txt.
  • CI fails when a finding's count rises or a new key appears. The checker only reads the baseline.
  • Complexity diff, hotspot, consumer-import fitness, and the path_filters mutation job stay as they are on main.

Test plan

  • bash scripts/test-check-ruff.sh (empty ceiling fails, baselined finding passes, count rise fails, unknown finding fails, baseline file is not rewritten)
  • python3 scripts/check-ruff.py src tests passes on this tree
  • Lint job on this PR stays green

Made with Cursor

The E/F gate is already clean. Freeze that ceiling so a new finding fails and CI cannot rewrite the baseline to hide it.

Co-authored-by: Cursor <cursoragent@cursor.com>
@jmjava
jmjava merged commit e84b383 into main Oct 11, 2026
8 checks passed
@jmjava
jmjava deleted the ratchet/docgen-ruff-baseline branch October 13, 2026 02:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant