-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Don't run flake8 twice in CI #15129
Don't run flake8 twice in CI #15129
Conversation
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.
Hm good spot, but I'm not sure about this, since it's nice to have the guarantee that tox
works. But don't feel strongly!
Edit: I guess we could remove flake8 from precommit, which is the slowest thing in the lint step
Yeah. I wondered if we should maybe delete the
People who have pre-commit set up locally will probably want to run flake8 as part of pre-commit. But if we want it run separately, we could possibly skip it for CI runs of pre-commit, like we do at typeshed, and run it separately using GitHub Actions: https://github.com/python/typeshed/blob/9abf620500644509a0ba656767e858ac2ef23dd6/.pre-commit-config.yaml#L41-L46 |
This comment has been minimized.
This comment has been minimized.
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.
Thank you!
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉 |
We now run flake8, black and isort on PRs using
pre-commit.ci
. This is faster than usingtox
on GitHub Actions, and for black and isort, it also autofixes PRs (and the check in CI fails if it can't autofix a PR).