Git Hooks

Hooks run on named Git events from the effective path. Git ignores non-executable files; failed pre-hooks abort, post-hooks do not.

Locate the effective hooks

git rev-parse --git-path hooks
git rev-parse --git-common-dir
git config --show-origin --get core.hooksPath

--git-path hooks resolves the path: $GIT_DIR/hooks normally, $GIT_COMMON_DIR/hooks in linked worktrees. Relative core.hooksPath follows hook cwd (non-bare clients: worktree root; bare/receive: $GIT_DIR).

Distribution

Clones omit source .git/hooks; templates can seed hooks and core.hooksPath can redirect to shared/global hooks. After reviewing and trusting the scripts, use a tracked directory:

git config core.hooksPath .githooks
git commit --no-verify          # bypass pre-commit + commit-msg
git push --no-verify            # bypass pre-push

Visibility and checkout scope

• A custom zsh chpwd function can list executable non-.sample hooks once per path; call it at shell startup too, and avoid alert fatigue.
• A .pre-commit-config.yaml declares checks, not an installed hook. Installer-marker checks miss custom wrappers.
• Sharing a working copy can bring active .git metadata. Linked worktrees share common-dir hooks; see Git worktrees.

Client-Side

Commit flow: pre-commit → prepare-commit-msg → editor → commit-msg → post-commit.

Patch flow (git am): applypatch-msg → pre-applypatch → post-applypatch.

Server-Side (on bare repo)

update is the granular gatekeeper: protect branches, reject non-FF on main, require signed commits.

pre-push and pre-receive receive ref-update records on stdin; read them when validating refs.

Pitfalls

• For Bash hooks, use set -euo pipefail; POSIX sh lacks pipefail.
• core.hooksPath replaces the default dir; copy any needed defaults in.
• Client hooks are advisory; enforce security server-side or in CI.
• Prompt listings are visibility aids, not hook validation or enforcement.

See source and validation notes.