Lesson 16 of 20

6 mins read

Git Hooks & Automated Quality Assurance (Pre-Commit)

In Plain English

Git Hooks are executable custom scripts located in .git/hooks/ that trigger automatically at pivotal lifecycle events (pre-commit, commit-msg, pre-push, post-merge). Modern engineering teams enforce linting, formatting (Prettier/clang-format), and test runs before allowing commits to proceed.

The Mental Model

"Git Hooks are automatic quality control gates on a car assembly factory: before a car rolls to the next station (pre-commit), automated sensors check tire pressure and bolt tightness—stopping the line if an error is detected."

Deep Dive: How It Works

pre-commit: Runs before commit message prompt; exiting with non-zero aborts the commit.

commit-msg: Validates message format (e.g. enforcing Conventional Commits regex pattern).

pre-push: Runs test suites before allowing bytes to transmit to remote servers.

Syntax Blueprint

#!/bin/sh
# .git/hooks/pre-commit
pytest tests/ || exit 1
chmod +x .git/hooks/pre-commit

Create executable shell script in .git/hooks/ to enforce quality checks before commits.

Core Rules to Remember

Zero-Cost Gatekeeping: Prevents broken builds or unformatted code from ever entering repository history.

Hook Sharing: Use core.hooksPath (.githooks/) or tools like Husky/pre-commit to share hooks across teams.

Bypassing Hooks: git commit --no-verify bypasses pre-commit and commit-msg hooks in rare emergencies.

Common Beginner Traps & How to Fix Them

Mistake:Creating a hook file in .git/hooks/ but forgetting to grant executable permissions (chmod +x).

Why it happens: New files on Unix are created without execute bits by default.

How to fix: Run chmod +x .git/hooks/<hook-name>.

Pro Tip: Configure git config core.hooksPath .githooks to track team hook scripts directly inside version control.

Live Interactive Example

Hit Run Code to see it live

Pre-Commit Hook Setup

Git 2.45 / CLI

Output Console

Click "Run Code" to view the rendered output.

How it works: The pre-commit hook runs automatically before the commit is finalized.

Your Turn: Micro Challenge

No pressure! Edit the starter code below and test your solution with instant feedback.

Micro Exercise

Configure Custom Hooks Path

Configure Git to use ".githooks" as the custom hooks directory with "git config core.hooksPath .githooks".
Verify with "git config core.hooksPath".

Sandbox Output

Click "Run & Check" to test your solution.

Finished reading and practicing?

Mark this lesson as completed to update your course progress.