Client-side vs server-side hooks in Git - When to Use Which

The Big Idea

What if your project could catch mistakes before they cause headaches for everyone?

The Scenario

Imagine you and your friends are working on a shared project. Every time someone makes a change, they have to remember to check if their code follows the rules before sharing it. Sometimes they forget, and mistakes sneak in.

The Problem

Relying on everyone to manually check their work is slow and risky. Mistakes can break the project, and fixing them later wastes time and causes frustration.

The Solution

Client-side and server-side hooks automatically check and enforce rules at different stages. Client-side hooks catch issues before changes leave your computer, while server-side hooks protect the shared project by checking changes before they are accepted.

Before vs After

✗ Before

Remember to run tests and style checks before commit

✓ After

Use a client-side hook to run tests automatically before commit

What It Enables

This makes teamwork smoother and safer by catching problems early and keeping the shared project healthy.

Real Life Example

A developer tries to commit code with a typo. The client-side hook stops the commit and asks to fix it. Another developer pushes code to the server, but the server-side hook rejects it because tests fail, preventing broken code from entering the project.

Key Takeaways

Manual checks are slow and error-prone.

Client-side hooks catch problems before code leaves your computer.

Server-side hooks protect the shared project by validating incoming changes.