Closed extreme4all closed 1 year ago
Id recommend adding pre-commit as a whole instead of individual workflows to GHA. This allows you to just update the pre-commit config file with any new tools that are used for the project, such as flake8 or import sorting. Pre-commit can also run before committing, hence the name, which should catch any issues first.
Id recommend adding pre-commit as a whole instead of individual workflows to GHA. This allows you to just update the pre-commit config file with any new tools that are used for the project, such as flake8 or import sorting. Pre-commit can also run before committing, hence the name, which should catch any issues first.
when going through the documentation, i see the developer has to:
pre-commit install
and to run them
pre-commit run
This does not seem automatic to me or am wrong here?
The only step that wouldn't be automatic is the first command. You don't have to run pre-commit run
as that would run automatically when creating a new commit
@LukeHankey sure sounds good then, can we also use the pylintrc found in https://google.github.io/styleguide/pyguide.html, with a few modifications?
@LukeHankey , @ThorntonMatthewD couldn't commit with precommit. this also requires local instalation. just python black on PR, that tells you what files & lines do not pass the linting would be perfect
code should be formatted with python black