{"id":1399,"date":"2024-09-08T00:00:00","date_gmt":"2024-09-07T22:00:00","guid":{"rendered":"https:\/\/demo.sidekick.be\/itenium\/git-hooks-with-husky-v9\/"},"modified":"2025-11-28T13:31:42","modified_gmt":"2025-11-28T12:31:42","slug":"git-hooks-with-husky-v9","status":"publish","type":"post","link":"https:\/\/demo.sidekick.be\/itenium\/blog\/dev-setup\/git-hooks-with-husky-v9\/","title":{"rendered":"Git Hooks with Husky v9"},"content":{"rendered":"

Hooks<\/h1>\n
\n

git hooks<\/strong>
Run a program before certain points in gits execution.
pre-commit<\/code> and pre-push<\/code> hooks are probably the most interesting.<\/p>\n<\/blockquote>\n

They are defined in .git\/hooks<\/code>. You can find some example files in that directory. Remove their .sample<\/code> suffix to test them out.<\/p>\n

The githooks are saved locally and not pushed to the remote. This is obviously a problem when working in a team but the .git\/hooks<\/code> folder can be changed globally or for the current repository with the core.hooksPath<\/code><\/a> setting.<\/p>\n

This is obviously never going to happen but you could skip githooks with:<\/p>\n

git commit --no-verify\ngit push --no-verify\n\n# Or if you want to really quickly skip it ;)\ngit commit -n\n<\/code><\/pre>\n
Husky<\/h1>\n
Or, use Husky to easily make the git hooks part of the repository itself and share it with the entire team.<\/p>\n
npm install husky --save-dev\nnpx husky init\n<\/code><\/pre>\n
This will add a prepare<\/code> npm script in your package.json<\/code>. The prepare script runs after an npm install<\/code> to ensure things are setup for everyone.<\/p>\n
\"scripts\": {\n  \"prepare\": \"husky\"\n},\n<\/code><\/pre>\n
And it creates a .husky\/pre-commit<\/code> which you can try out by doing a git commit<\/code>!
 Avoid having to git reset HEAD~<\/code> all the time by ending your script with exit 1<\/code> while testing\/setting it up.<\/p>\n
Finally it sets the core.hooksPath<\/code> to .husky\/_<\/code>. Husky creates files in that directory to link all githooks with the h<\/code> shell script which will execute a .husky\/SOME_GITHOOK<\/code> if it exists.
 Husky also adds a gitignore to the _<\/code> folder to keep the generated files out of your git repository.<\/p>\n
git config core.hooksPath\n# --> .husky\/_\n<\/code><\/pre>\n
Script h<\/code><\/h2>\n
In this order:<\/p>\n