There are several types of Git hooks that can be used to automate tasks and enforce policies throughout the Git workflow[1][2][3][4][5]:
Client-Side Hooks
pre-commit: Runs before a commit is created. It can be used to check the staged changes for code style violations, syntax errors, or to run tests[1][2][4].
prepare-commit-msg: Executes before the commit message editor is opened, but after the default message has been set. It can be used to add information to the commit message[1][2][4].
commit-msg: Runs before the commit is completed, but after the commit message has been created. It can be used to verify the format or content of the commit message[1][2][4].
post-commit: Triggered after a commit is made. It can be used to perform actions such as sending notifications or updating documentation[1][2][4].
pre-rebase: Runs before a rebase operation starts. It can be used to perform checks or actions to ensure that the rebase can proceed smoothly[2][4].
post-checkout: Runs after a git checkout operation. It can be used to set up a working directory or auto-generate documentation[1].
post-merge: Triggered after a merge is completed. It can be used to perform actions such as up...
