chore: add focused pre-push vulture guard#1251
Conversation
c903925 to
1953fee
Compare
|
Closing — this PR copies @seroperson's 1. Self-admission in the linked issue #1250. Filed by you 5 minutes before this PR, body reads: "While analyzing the 2. Source commit predates yours by 30 minutes.
3. Byte-identical files on the overlap. This PR touches 14 files; all 14 are a subset of #1253's 20, and 12 of the 14 are byte-identical with #1253 — same imports removed, same functions deleted, same whitespace, same
Independent dead-code discovery across Account profile carries no identifying signal (no name, bio, location, 0 followers/following) — low-trust posture for a contributor lifting another open branch without attribution. Closing. |
Summary
Closes #1250
Adds
vultureas a pre-push dead-code guard and wires it into the existing CI pre-push lane. The goal is to keep unused Python helpers, stale test fixtures, and framework leftovers from accumulating after one-off cleanup PRs.Changes
vulture==2.16to the dev dependency set anduv.lock.vulturehook in.pre-commit-config.yaml.[tool.vulture]configuration with project paths, excludes, and framework-specific ignores.Out of scope
Type of Change
Testing
Validation:
Results:
pytest:725 passedpyright:0 errors, 0 warnings, 0 informationsvulture,ruff, pre-commit, and whitespace checks: passedChecklist