This content originally appeared on DEV Community and was authored by Aryan Dev Shourie
Introduction to Git Hooks
Git is more than just a version control system. It also provides automation to improve developer productivity. One of these features is Git Hooks.
Git Hooks are scripts that Git automatically executes before or after specific events, such as commiting code, pushing to a remote repository or merging branches. They allow developers to automate tasks seamlessly within the Git workflow.
In simpler words, Git Hooks act like "triggered scripts" that run at different stages of Git's lifecycle.
The need for Git Hooks
Without Git Hooks, maintaining consistent standards across a team can be difficult. For example, the following issues may arise:
Developers may forget to run linting or tests before committing.
Sensitive files like API keys or credentials might accidentally get pushed.
Commit messages may lack standard formatting, making history harder to read.
Git Hooks solve these problems by automating checks and enforcing rules. Instead of relying on developers to remember every step, Git Hooks ensure quality and consistency by running predefined scripts automatically.
Types of Git Hooks available
Git provides a variety of Hooks that can be used in different stages of the workflow. These are categorized into two types:
Client-Side Hooks: Triggered by operations like committing, merging, or rebasing. Example: pre-commit, prepare-commit-msg, commit-msg.
Server-Side Hooks: Triggered on the server side when pushes are received. Example: pre-receive, update, post-receive.
How to find Git Hooks
When you initialize a Git repository, Hooks are available as sample scripts inside the .git/hooks/ directory. You can verify by using this command:
ls .git/hooks/
You will see files like pre-commit.sample, pre-push.sample etc. These sample files are not active by default, you can make them active by removing the .sample extension from the filename.
Example Usage of a Git Hook: Pre-Commit with Linter
Let's go through a step-by-step guide of setting up a pre-commit Hook to block commits if linting errors exist in the staged files.
Step 1: Navigate to the Hooks directory
cd .git/hooks/
Step 2: Create/Edit the Pre-Commit Hook
nano pre-commit
Step 3: Add the Hook script
Here is an example script to check for ESLint issues before allowing a commit:
#!/bin/sh
echo "Running lint checks..."
# Run ESLint on staged JavaScript files
STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM | grep '\.js$')
if [ "$STAGED_FILES" = "" ]; then
exit 0
fi
# Run eslint
npx eslint $STAGED_FILES
if [ $? -ne 0 ]; then
echo "❌ Lint errors found. Commit aborted."
exit 1
fi
echo "✅ Lint checks passed!"
exit 0
Step 4: Make it executable
chmod +x .git/hooks/pre-commit
Step 5: Test the Hook
Modify a .js file with linting issues.
Try committing:
git add file.js
git commit -m "Test commit"
- If issues are found, the commit will be blocked until you fix them. This ensures that no developer can commit code with linting errors.
Advantages of Git Hooks
Automation: Automates repetitive tasks like running tests, linting, or formatting.
Consistency: Enforces code quality and project standards across the team.
Security: Prevents accidental commits of sensitive files or bad code.
Efficiency: Saves time by catching issues early, before code is pushed.
Flexibility: Hooks can be customized for different workflows and tools.
With Git Hooks in place, teams can maintain higher code quality, enforce rules effortlessly, and automate mundane checks—all directly within Git’s workflow.
And that's it! This was just a quick overview about using Git Hooks in your daily workflow.
Connect with me on LinkedIn :- Linkedin
Do check out my GitHub for amazing projects :- Github
This content originally appeared on DEV Community and was authored by Aryan Dev Shourie
Aryan Dev Shourie | Sciencx (2025-08-23T09:44:54+00:00) Git Hooks: Automating Workflows in Git. Retrieved from https://www.scien.cx/2025/08/23/git-hooks-automating-workflows-in-git/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.