- Notifications
You must be signed in to change notification settings - Fork673
refactor: pre-commit triggered from tox#2320
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
I personally don't like this as I do NOT use pre-commit. I like to do everything in tox. And I do not want to use pre-commit. |
b6f5bf3
todd7730e
Compare
Good point. I should have raised this topic in a discussion. |
29cafad
toca5b6a7
CompareUh oh!
There was an error while loading.Please reload this page.
0042e7a
to214c2d7
CompareUh oh!
There was an error while loading.Please reload this page.
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.
This works for me. As I usually run a subset of the tox checks in my development process.
I like that I don't have to runpre-commit
and can just usetox
🙂
So I approve but let@nejch do the merging if he approves.
|
Uh oh!
There was an error while loading.Please reload this page.
The project is using two liniting frameworks: tox and pre-commit. Each has its own configuration files and a CI workflow.
The purpose of this PR is to consolidate linting into one framework: tox
Discussion -#2321
This PR is a baby step towards a full transition