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.

Practice

1. What is the main purpose of Git hooks in a project?

easy

A. To create new branches automatically

B. To store large files outside the repository

C. To merge branches without conflicts

D. To automatically run scripts during Git actions

Solution

1. Step 1: Understand what Git hooks do

   Git hooks are scripts that run automatically when certain Git events happen, like committing or pushing.

2. Step 2: Identify the main purpose

   The main purpose is to automate tasks during Git actions, such as checks or notifications.

3. Final Answer:

   To automatically run scripts during Git actions -> Option D

4. Quick Check:

   Git hooks automate scripts = A [OK]

Hint: Hooks run scripts automatically on Git events [OK]

Common Mistakes:

• Confusing hooks with branch management
• Thinking hooks store files
• Assuming hooks merge branches

2. Which of the following is the correct way to enable a Git hook script?

easy

A. Push the script to the remote repository

B. Add the script to the .gitignore file

C. Rename the script to remove the .sample extension in .git/hooks/

D. Create a new branch named hooks

Solution

1. Step 1: Locate Git hooks directory

   Git hooks are stored in the .git/hooks/ folder, usually with .sample extensions.

2. Step 2: Enable a hook script

   To enable a hook, you rename the script to remove the .sample extension so Git can run it.

3. Final Answer:

   Rename the script to remove the .sample extension in .git/hooks/ -> Option C

4. Quick Check:

   Remove .sample to enable hook = C [OK]

Hint: Remove .sample extension to activate hook scripts [OK]

Common Mistakes:

• Adding hooks to .gitignore disables them
• Pushing hooks doesn't enable them locally
• Creating branches does not enable hooks

3. Given a pre-commit hook script that checks for TODO comments and rejects the commit if found, what will happen if you try to commit a file containing 'TODO: fix this'?

medium

A. The commit will be rejected with a warning about TODO comments

B. The commit will delete the TODO comments automatically

C. The commit will succeed but add a warning in the commit message

D. The commit will succeed without any message

Solution

1. Step 1: Understand the pre-commit hook behavior

   The pre-commit hook runs before the commit is finalized and can reject commits based on conditions.

2. Step 2: Analyze the effect of TODO comments

   If the script finds 'TODO' comments, it rejects the commit and shows a warning message.

3. Final Answer:

   The commit will be rejected with a warning about TODO comments -> Option A

4. Quick Check:

   Pre-commit rejects TODO commits = D [OK]

Hint: Pre-commit hooks can block commits with errors [OK]

Common Mistakes:

• Assuming commit succeeds silently
• Thinking commit adds warnings instead of blocking
• Believing hooks modify code automatically

4. You wrote a post-commit hook script but it does not run after commits. What is the most likely reason?

medium

A. The script is named post-commit.sample

B. All of the above

C. The script file is missing execute permissions

D. The script is located outside the .git/hooks directory

Solution

1. Step 1: Check script permissions

   Git requires hook scripts to have execute permissions to run.

2. Step 2: Check script name and location

   The script must be named exactly (no .sample) and be inside .git/hooks/ folder.

3. Step 3: Combine all issues

   Any of these issues (wrong name, wrong location, no execute permission) will prevent the hook from running.

4. Final Answer:

   All of the above -> Option B

5. Quick Check:

   Permissions, name, location all matter = D [OK]

Hint: Check permissions, name, and location for hooks [OK]

Common Mistakes:

• Ignoring execute permissions
• Leaving .sample extension
• Placing script outside hooks folder

5. You want to automate sending a notification email after every successful push to the remote repository. Which Git hook should you use and why?

hard

A. post-push hook, because it runs after the push completes successfully

B. pre-push hook, because it runs before pushing and can stop the push

C. post-commit hook, because it runs after each commit locally

D. pre-commit hook, because it runs before committing changes

Solution

1. Step 1: Identify when to send notification

   The notification should be sent after a successful push to the remote repository.

2. Step 2: Understand available hooks

   Git does not have a built-in post-push hook, but the server-side post-receive hook runs after a successful push on the remote repository.

3. Step 3: Choose the best hook

   To send notification after a successful push, use the server-side post-receive hook, which runs after the push completes successfully.

4. Final Answer:

   post-push hook, because it runs after the push completes successfully -> Option A

5. Quick Check:

   Use post-push (server-side post-receive) for notifications after push = A [OK]

Hint: Use post-receive hook on server to notify after push [OK]

Common Mistakes:

• Assuming post-push hook exists locally in Git
• Using pre-push which runs before push
• Using post-commit which runs too early