Closed dheavy closed 3 months ago
After a quick investigation, this is due to not being in the virtual env while doing a commit.
I'll propose a PR to the CONTRIBUTING
file to make it clear...
...and/or change the pre-commit config to have it use the current python (which is not necessarily system
, it could be one from a venv)
Describe the bug When committing changes, the pre-commit task is ran. It currently fails at the
pytest
step with the following error:To Reproduce Steps to reproduce the behavior:
Expected behavior The pre-commit hook passes, unless a test isn't green.
Screenshots
Desktop (please complete the following information):
Additional context
Finalizing the pre-commit hook de-incentivizes contributor to bypass it with
--no-verify
. Furthermore, its task could be added to the Github actions pipeline. All of which would help streamline contributions for a more stable code base.