4 ms·
I've never used the `pre-commit` framework, but it's really simple to wire up arbitrary shell scripts; check out the `.git/hooks` directory in your repo for sa
by theptip 6y ago
I've never used the `pre-commit` framework, but it's really simple to wire up arbitrary shell scripts; check out the
`.git/hooks` directory in your repo for samples, e.g. `.git/hooks/pre-commit.sample`.
You can run any old shell script there, without having to install a python tool.
- westurner 6y agoYeah but that githook will only be installed on that one repo on that one machine. And they may have no or a different version of bash installed (on e.g. MacOS or Windows). IMHO, POSIX-compatible portable shell scripts are more trouble than portable Python scripts. Pre-commit requires Python and pre-commit to be installed (and then it downloads every hook function). This fetches the latest version of every hook defined in the .pre-commit-config.yml: pre-commit autoupdate https://pre-commit.com/#pre-commit-autoupdate https://pre-commit.com/#pre-commit-autoupdate A person could easily `ln -s repo/.hooks/hook*.sh repo/.git/hooks/` after every git clone.