ci: add fallow audit job (PR-scoped, new-only gate)#942
Merged
jrusso1020 merged 1 commit intoMay 19, 2026
Conversation
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
miguel-heygen
approved these changes
May 18, 2026
5 tasks
This was referenced May 19, 2026
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
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.

What
Adds a
Fallow auditjob to CI that runs on PRs and fails when new dead-code, complexity, or duplication issues are introduced into the changed files.Why
After #938 landed a fallow config + the first round of cleanup, the codebase still has ~276 inherited dead-code findings, ~482 clone groups, and ~680 functions above complexity thresholds. Fixing those is a multi-PR effort. Until then, we want to stop bleeding: prevent new debt from sneaking in via PRs.
How
fallow audit --base origin/main --fail-on-issuesuses the default--gate new-only, which compares the PR's findings against the base-snapshot and only counts findings introduced by the changeset. Inherited findings still appear in the log for visibility but don't fail the build.Behavior verified locally:
Pinned to
fallow@2.75.0— the same version that produced the current.fallowrc.jsonc. Bumps will land via deliberate PRs, not transitivelatestshifts.The job runs only on PRs (
github.event_name == 'pull_request') since audit needs a base to diff against, and is gated behind the existingDetect changesjob so docs-only PRs skip it.Test plan
python3 -c 'import yaml; yaml.safe_load(...)')Follow-ups
fallow fix --auto-fixablecovers the bulk of the 228 unused-export findings; stacked PR will land next--format pr-comment-githubfor inline review comments