🎨 Move to pre-commit linters #66
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azogue
force-pushed
the
proposal/new-lint-rules
branch
2 times, most recently
from
11ac370
to
35dacdc
Compare
with ruff, isort, black, and mypy.
to normalize format on yaml and markdown files
and fix typo on library name in contribute.md
and sync markdown in root and docs
and update used revisions to latest
azogue
force-pushed
the
proposal/new-lint-rules
branch
from
fe97530
to
e4dbbda
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cc @sabuhish
Related to this proposal, this is my opinionated view 🙈
pre-commitconfiguration, usingruff+isort+blackprettier+mypyto automatically format and analyse each code change, making it easy for collaborators to contribute 💪makefileand shell scripts to install a development environment, and refer topoetrymethods