Tooling: add git hooks to help maintain codebase #35
Conversation
This file contains hidden or 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
Guts
force-pushed
the
tooling/add-git-hooks
branch
from
9856d5d to
54678aa
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.
I propose to add some git hooks to apply some of current linters (ruff, basic controls) and formatters (black, isort) to the existing code base.
It's a kind of my toolbelt to work on Python projects and it helps especially for those I don't have much time to maintain regularly.
This PR proposes a configuration for the well-known pre-commit framework and apply formatters and fix minor static errors to the existing codebase.