Hooks de Git del lado del cliente
Comprenda e implemente hooks del lado del cliente, como `pre-commit` y `post-merge`, para aplicar estándares localmente.
Hooks de Git del lado del cliente es una lección gratuita de Git Advanced: Monorepo, Submodules & Workflows en CoddyKit. Esta es la lección 1 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Git Advanced: Monorepo, Submodules & Workflows, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Git Advanced: Monorepo, Submodules & Workflows incluye 4 lecciones en total.
Partes de esta lección aún no han sido traducidas y se muestran en inglés.
Intro to Git Hooks
Welcome! In this lesson, you'll learn about Git hooks. These are scripts that Git automatically runs before or after events like committing, merging, or pushing.
Think of them as automated assistants for your Git workflow. They help enforce project standards and automate routine tasks.
Client-Side vs. Server-Side
Git hooks come in two flavors:
- Client-side hooks: Run on your local machine. They only affect your personal repository. Examples include `pre-commit` and `post-merge`.
- Server-side hooks: Run on the Git server. They affect all pushes to the repository. We'll cover these in a later lesson.
This lesson focuses on client-side hooks and how to use them locally.
Where Hooks Live
All Git hooks are stored in the .git/hooks directory within your repository. When you initialize a new Git repository, Git populates this directory with sample hook scripts.
Let's take a look inside a typical .git/hooks folder:
ls -F .git/hooks/Activating a Hook
By default, the sample hook scripts end with .sample, making them inactive. To activate a hook, you need to:
- Remove the
.sampleextension from its filename. - Make the script executable.
Let's activate the pre-commit hook by renaming and making it executable:
cd .git/hooks
mv pre-commit.sample pre-commit
chmod +x pre-commit`pre-commit`: Your Local Guard
The pre-commit hook is one of the most useful client-side hooks. It runs just before Git asks you for a commit message and before the actual commit is created.
If the script exits with a non-zero status, Git aborts the commit. This makes it perfect for:
- Running linters (e.g., ESLint, Flake8)
- Executing unit tests
- Checking for common mistakes (e.g., debug statements)
Example: `pre-commit` for Linting
Here's a simple pre-commit script that checks if any staged files contain the word "TODO". If it finds "TODO", the commit is blocked.
You can edit the .git/hooks/pre-commit file directly to add this content:
#!/bin/sh
# Check for 'TODO' in staged changes
if git diff --cached | grep -q "TODO"; then
echo "Error: 'TODO' found in staged changes. Please resolve before committing."
exit 1
fiTesting the `pre-commit` Hook
Now, let's try to commit a file that contains "TODO". The pre-commit hook should prevent the commit.
First, create a file with "TODO", then try to commit it:
echo "This is a file with a TODO item." > my_feature.txt
git add my_feature.txt
git commit -m "Attempt to commit with TODO"`post-merge`: After the Merge
The post-merge hook runs immediately after a successful git merge or git pull (which is essentially a fetch followed by a merge or rebase).
It's useful for automating tasks that should happen after your working directory has been updated by a merge, such as:
- Installing new dependencies
- Rebuilding your project
- Updating documentation or symlinks
Example: `post-merge` for Dependencies
Imagine you're working on a project with Node.js. After merging a branch that introduced new dependencies (updated package.json), you'd want to run npm install.
Here's a post-merge script that checks if package.json was changed by the merge and runs npm install if it was:
#!/bin/sh
# Run npm install if package.json changed
if git diff --name-only HEAD@{1} HEAD | grep -q "package.json"; then
echo "package.json changed, running npm install..."
# npm install # Uncomment in a real project
echo "(npm install simulated)"
fiHook Challenge
You've learned about client-side Git hooks! Which of the following statements are TRUE about them?
Client-Side Hooks: Recap
Great job! You've successfully explored client-side Git hooks. Here's what we covered:
- What they are: Scripts that run automatically at specific Git events.
- Where they live: In the
.git/hooksdirectory. - How to activate: Rename from
.sampleand make executable. - `pre-commit`: Runs before a commit, useful for validation and linting.
- `post-merge`: Runs after a merge, good for dependency updates or rebuilding.
Client-side hooks are powerful tools for personal workflow automation and local quality checks!
Preguntas frecuentes
¿La lección «Hooks de Git del lado del cliente» es gratis?
Sí — el texto completo de «Hooks de Git del lado del cliente» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Git Advanced: Monorepo, Submodules & Workflows, actualiza a CoddyKit PRO. El curso de Git Advanced: Monorepo, Submodules & Workflows incluye 4 lecciones en total.
¿Qué aprenderé en «Hooks de Git del lado del cliente»?
Comprenda e implemente hooks del lado del cliente, como `pre-commit` y `post-merge`, para aplicar estándares localmente. Practicas Git Advanced: Monorepo, Submodules & Workflows con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.
¿Necesito experiencia previa para empezar Git Advanced: Monorepo, Submodules & Workflows?
No se requiere experiencia previa. Git Advanced: Monorepo, Submodules & Workflows en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 1 de 4.
¿Cuánto tiempo toma la lección «Hooks de Git del lado del cliente»?
La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.
¿Puedo escribir y ejecutar código en esta lección de Git Advanced: Monorepo, Submodules & Workflows?
Sí. Cada lección de Git Advanced: Monorepo, Submodules & Workflows incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.
Todas las lecciones de este curso
- Hooks de Git del lado del cliente
- Hooks de Git del lado del servidor
- Configuración y alias de Git
- Compartir hooks con el equipo mediante Husky