Hook Git Sisi Klien
Pahami dan terapkan hook sisi klien seperti `pre-commit` dan `post-merge` untuk menegakkan standar secara lokal.
Hook Git Sisi Klien adalah pelajaran Git Advanced: Monorepo, Submodules & Workflows gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Git Advanced: Monorepo, Submodules & Workflows, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Git Advanced: Monorepo, Submodules & Workflows mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
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!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Hook Git Sisi Klien” gratis?
Ya — teks lengkap “Hook Git Sisi Klien” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Git Advanced: Monorepo, Submodules & Workflows, upgrade ke CoddyKit PRO. Kursus Git Advanced: Monorepo, Submodules & Workflows mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Hook Git Sisi Klien”?
Pahami dan terapkan hook sisi klien seperti `pre-commit` dan `post-merge` untuk menegakkan standar secara lokal. Kamu berlatih Git Advanced: Monorepo, Submodules & Workflows dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Git Advanced: Monorepo, Submodules & Workflows?
Tidak diperlukan pengalaman sebelumnya. Git Advanced: Monorepo, Submodules & Workflows di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.
Berapa lama pelajaran “Hook Git Sisi Klien” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Git Advanced: Monorepo, Submodules & Workflows ini?
Ya. Setiap pelajaran Git Advanced: Monorepo, Submodules & Workflows menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Hook Git Sisi Klien
- Hook Git Sisi Server
- Konfigurasi dan Alias Git
- Berbagi Hook dengan Tim Menggunakan Husky