-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
pre-commit run --all-files fails on main branch #1674
Comments
@aignas could I pick this up? To ask questions on how I can start, can I reach out in this issue thread? (or on slack?) |
Yep, go for it! Feel free to keep notes in the contributing.md on your experience (the sections on setting up pyenv and pre-commit came from my experience getting started, but they're incomplete as I forgot some details). |
@chethanagopinath Do you still plan on working on this? I'd be happy to take it over if you don't have time. |
@dougthor42 This issue seems to have dropped off my radar for some reason. Thanks for reaching out, please feel free to pick it up. |
Run `isort` and `black` on all python files so that the pre-commit hooks do not fail anymore. It seems like most of the issues were quotation marks and vertical whitespace. Fixes #1674.
🐞 bug report
Description
Running
pre-commit run --all-files
produces errors from incorrectly formatted Python files, with bothblack
andisort
complaining. If a project usespre-commit
, I would expect the state of the main branch to pass all thepre-commit
checks, to facilitate further development.🔬 Minimal Reproduction
Check out the
main
branch, at the time of writing 69edec8. Make suregit status
reports a clean tree. Runpre-commit run --all-files
. Expected behavior is to see all checks "Passed".🔥 Exception or Error
🌍 Your Environment
Operating System:
Output of
bazel version
:Rules_python version:
Latest
main
(69edec8 at the time of writing)Anything else relevant?
The text was updated successfully, but these errors were encountered: