Thanks for taking a look! Locally you could set up pre-commit/pre-push hooks to only assess changed files (`tff check --since main`). I just realized you cannot assert changed files directly yet. In CI you can configure the bot to do the same: https://tff.readthedocs.io/en/latest/ci_cd/?h=only#1-crucial....
Looks very promising!
Now I have to decide which of the ERR lints we want to fix and which to exclude :)
Thanks for taking a look! Locally you could set up pre-commit/pre-push hooks to only assess changed files (`tff check --since main`). I just realized you cannot assert changed files directly yet. In CI you can configure the bot to do the same: https://tff.readthedocs.io/en/latest/ci_cd/?h=only#1-crucial....
Yep that's exactly what I would want to do
I was impressed that it 'just worked' on my dbt project
We're currently using sqlfluff linting but it was a bit finicky to get the pieces configured.
sqlfluff does have linting inside VS Code too though, when it works (python path issues...)