Open ben-nathanson opened 3 years ago
Normally, git hooks are not tracked. This means we couldn't put them in source control directly.
We could create a hooks
directory and have every contributor manually configure their git hook path to the hooks
directory. This would be a one-time step. If we want to avoid that, we could extend the documentation to include a step to this hook in the setup flow.
We could use pre-commit
, a library for Python3 which should do this automatically.
I'll bring this back to the next meeting and see what folks think.
Rather than having to remember to run
black .
the consensus from tonight's meeting was that it would be great to have this as a pre-commit hook. I will work on an implementation to explore the idea.