Closed zacharyburnett closed 2 months ago
I always get this mixed up but does adding this file also mean the pre-commit bot will auto-fix PRs?
I'm also failing to find where pre-commit
runs in the CI.
Perhaps we need a new workflow to run pre-commit (perhaps like the one in asdf).
We could also enable the bot (but I don't trust it as you already know).
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 59.60%. Comparing base (
ccf871a
) to head (f89b828
). Report is 7 commits behind head on master.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:-O I think we should dial back those pre-commit hooks or exclude more files. The log for the pre-commit job is over 50k lines long...
:-O I think we should dial back those pre-commit hooks or exclude more files. The log for the pre-commit job is over 50k lines long...
yeah it looks like it was ruff format
, trim-trailing-whitespace
, and end-of-file-fixer
. I thought they would only run on changed files, though...
uses
pre-commit
for linting, formatting, and security checking. By default,pre-commit
is run only on changes lines. Putting these checks in.pre-commit-config.yaml
ensures that we can pin theruff
version to make sure that new rules don't break style checks randomlyChecklist for PR authors (skip items if you don't have permissions or they are not applicable)
CHANGES.rst
within the relevant release section~