Skip to content

chore: exclude test fixtures from the sql-sop dogfooding pre-commit hook #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pawansingh3889 merged 1 commit into from
May 9, 2026
Merged

chore: exclude test fixtures from the sql-sop dogfooding pre-commit hook #51

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions .pre-commit-config.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,11 +37,16 @@ repos:
- id: ruff-format

# ── sql-sop dogfooding itself ─────────────────────────────────────
# Runs sql-sop on the project's own fixtures + any staged .sql files
# so a regression in a rule is caught before it ships.
# Runs sql-sop on staged .sql files so a regression in a rule is
# caught before it ships. Test fixtures under ``tests/fixtures/`` are
# excluded because those files deliberately contain bad SQL
# (E001..E006, S001..S003, etc.) to drive the rule unit tests --
# running the linter against them is guaranteed to fail and was
# turning pre-commit.ci red on every PR.
- repo: https://github.com/Pawansingh3889/sql-guard
rev: v0.7.0
hooks:
- id: sql-sop
args: [--severity, error]
files: \.sql$
exclude: ^tests/fixtures/
Loading