-
Notifications
You must be signed in to change notification settings - Fork 171
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.
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
move ruff
and bandit
checks to pre-commit
#8646
move ruff
and bandit
checks to pre-commit
#8646
Conversation
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 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). |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #8646 +/- ##
=======================================
Coverage 59.60% 59.60%
=======================================
Files 391 391
Lines 39286 39286
=======================================
Hits 23418 23418
Misses 15868 15868 ☔ View full report in Codecov by Sentry. |
Co-authored-by: Brett Graham <[email protected]>
:-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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Once this is merged the branch protection rules can be updated to check for pre-commit
instead of check-style
.
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)
added entry inCHANGES.rst
within the relevant release sectionupdated or added relevant testsran regression tests, post a link to the Jenkins job below.How to run regression tests on a PR
Make sure the JIRA ticket is resolved properly