Why hooks automate workflows in Git - Visual Breakdown

Process Flow - Why hooks automate workflows

Developer makes a change

↓

Git triggers hook script

↓

Hook script runs automated tasks

↓

Tasks succeed?

No→Stop commit or alert

Yes↓

Commit or push continues

Hooks run scripts automatically at key git events to check or enforce rules before continuing.

Execution Sample

Git

cat .git/hooks/pre-commit
#!/bin/sh
# Run tests before commit
npm test
if [ $? -ne 0 ]; then
  echo 'Tests failed, abort commit'
  exit 1
fi

A pre-commit hook runs tests and stops commit if tests fail.

Process Table

Step	Event	Hook Script Action	Result	Next Action
1	Developer runs git commit	pre-commit hook starts	Hook script runs npm test	Wait for test result
2	npm test runs	Tests pass	Exit code 0	Allow commit to continue
3	Commit completes	No errors	Commit saved	End
4	Developer runs git commit	pre-commit hook starts	Hook script runs npm test	Wait for test result
5	npm test runs	Tests fail	Exit code non-zero	Abort commit with message
6	Commit aborted	Error message shown	Commit not saved	End

💡 Commit continues only if hook script exits with code 0; otherwise commit is stopped.

Status Tracker

Variable	Start	After Step 2	After Step 5	Final
npm test exit code	N/A	0 (tests pass)	1 (tests fail)	Depends on test result
commit status	Not started	Allowed	Aborted	Final commit state

Key Moments - 3 Insights

Why does the commit stop when tests fail in the hook?

Because the hook script returns a non-zero exit code (see execution_table step 5), git stops the commit to prevent bad code.

Does the hook run automatically or does the developer have to run it manually?

Hooks run automatically on git events like commit (execution_table step 1), so the developer does not run them manually.

What happens if the hook script succeeds?

If the hook script exits with zero (step 2), git continues the commit normally (step 3).

Visual Quiz - 3 Questions

Look at the execution table, what is the npm test exit code when tests pass?

A 0

B 1

C 2

D Non-zero

💡 Hint

Check the 'npm test exit code' variable after step 2 in variable_tracker.

At which step does git abort the commit due to failing tests?

A Step 3

B Step 1

C Step 5

D Step 6

💡 Hint

Look at execution_table rows where tests fail and commit is aborted.

If the hook script always returns zero, what happens to the commit?

A Commit is always aborted

B Commit continues without interruption

C Hook script does not run

D Git shows an error

💡 Hint

Refer to execution_table step 2 and 3 where exit code 0 allows commit.

Concept Snapshot

Git hooks are scripts triggered automatically at git events like commit.
They run checks or tasks (e.g., tests) before allowing the action.
If a hook script exits with non-zero, git stops the action (like commit).
This automates workflows by enforcing rules without manual steps.
Hooks live in .git/hooks directory and run silently unless they block progress.

Full Transcript

Git hooks automate workflows by running scripts automatically during git events such as commits. For example, a pre-commit hook can run tests before the commit is saved. If tests fail, the hook script exits with a non-zero code, causing git to abort the commit and show an error message. If tests pass, the commit continues normally. This automatic running of scripts helps enforce rules and quality checks without the developer needing to run commands manually. Hooks are stored in the .git/hooks directory and activate on specific git actions, making workflows safer and more consistent.