Once installed, you do not have to do anything besides re-adding changed files if a pre-commit hook "failed" which just means, that a hook actually did something (like having to change files with go fmt). You can review what the hook actually did but it should not destroy anything.
You can, though, run the hooks manually with pre-commit run --all-files.
Python is required.
I added four hooks initially which you can see in the .pre-commit-config.yaml file.
This is very useful for development. (Automated
go fmt
especially before every commit :tada:)Refer to their page for installation instructions: https://pre-commit.com/#install
Once installed, you do not have to do anything besides re-adding changed files if a pre-commit hook "failed" which just means, that a hook actually did something (like having to change files with go fmt). You can review what the hook actually did but it should not destroy anything. You can, though, run the hooks manually with
pre-commit run --all-files
.Python is required.
I added four hooks initially which you can see in the
.pre-commit-config.yaml
file.