theglitchking/gimme-the-lint
Polyglot progressive linting — only NEW violations above the baseline block CI
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| mode | progressive (staged changes) or full (entire codebase) | no | full |
| fix | Auto-fix violations where the linter supports it | no | false |
| strict | Fail when a linter is missing for code that is present | no | false |
| verify | Also run the checks that need a live database or network (e.g. alembic-check: "you changed a model and forgot to generate a migration"). These can never run in a git hook — a pre-commit hook that dials a database fails on an aeroplane — so CI is the only place they belong, and the only place credentials legitimately live. Supply them as env/secrets on the job; gimme-the-lint reads the environment and never a committed config. | no | false |
| node-version | Node.js version | no | 22 |
| python-version | Python version (for Ruff); leave blank to skip Python setup | no | 3.13 |
| working-directory | Working directory (defaults to repo root) | no | . |
| comment-on-pr | Post the linting summary as a PR comment | no | true |
Outputs
| name | description |
|---|---|
| status | Overall result: pass or fail |
| new-violations | Number of new violations above the baseline |