Apa iku Git hooks lan paano digunakake?

Question

Accepted Answer

**Git hooks** minangka skrip sing Git jalani **kanthi otomatis** ing titik-titik tartamtu ing workflow Git (sadurunge/sawise commit, push, merge, lsp.). Dheweke ngawungake otomasi — paksane standar, nglakokake pemeriksaan, lan micu aksi — lan luwih-luwih digunakake kanggo kualitas kode lan integrasi CI.

## Apa iku hook

```text
Hooks are executable scripts in .git/hooks/ (or managed by tools) that Git runs on EVENTS:
  CLIENT-SIDE (local):
    pre-commit   → before a commit is created (lint, format, run quick tests)
    commit-msg   → validate/format the commit message
    pre-push     → before pushing (run tests, prevent pushing broken code)
    post-merge/checkout → after merge/checkout (e.g. reinstall dependencies)
  SERVER-SIDE (on the remote):
    pre-receive / update → enforce policies on push (reject bad pushes)
    post-receive → trigger deployment/CI/notifications after a push
```

## Panggunaan umum

```text
✓ pre-commit → LINT and FORMAT code; run quick tests; block secrets/debug code
  → catch issues BEFORE they're committed (fast feedback, consistent quality)
✓ commit-msg → enforce message format (e.g. Conventional Commits)
✓ pre-push → run the test suite → don't push failing code
✓ server-side → enforce policies; trigger CI/CD and deployments
```

## Ngatur hook ing tim

```text
⚠️ .git/hooks/ is LOCAL and NOT committed → hooks aren't shared automatically.
To share hooks across a team, use tools:
  → HUSKY (JS ecosystem), pre-commit (Python framework), lefthook, etc.
  → these version hooks in the repo and install them for everyone
→ Combined with CI: hooks give FAST LOCAL feedback; CI is the enforced safety net
  (hooks can be bypassed with --no-verify, so CI must also enforce).
```

## Apa rasane penting

Mangsuli Git hooks minangka pengetahuan tingkat senior sing berharga kanggo **ngotomasi pemeriksaan kualitas lan aksi workflow**, dadi migunani kanggo njaga kualitas kode lan integrasi karo CI/CD.

Hook ngawungake **otomasi ing acara Git kunci** — nglakokake skrip kanthi otomatis sadurunge/sawise commit, push, merge, lsp. — sing luwih-luwih digunakake kanggo paksane standar lan nyiyir masalah luwih awal.

Panggunaan paling umum lan berharga yaiku **pre-commit hook** kanggo nglakokake **linting, penyayating, tes cepet, lan deteksi rahasia sadurunge kode dikomit** — menehi umpan balik kanthi cepet lan njamin kualitas konsisten kanthi otomatis (dadi masalah digolek ing wektu commit tinimbang mengko ing CI utawa review), praktik sing abot-abot populer.

Panggunaan liyane (commit-msg hook paksane konvensi pesen kaya Conventional Commits, pre-push hook nglakokake tes kanggo ngeindari push kode sing rusak, lan hook server-side paksane kebijakan utawa micu CI/CD lan deployment) ngluwasi otomasi ing sakabaran workflow.

Mangsuli aspek **manajemen tim** praktis minangka penting: `.git/hooks/` minangka lokal lan **ora dikomit**, dadi hook ora dibagi kanthi otomatis — bagi hook ing sakumpulan tim mbutuhake alat kaya **Husky, pre-commit, utawa lefthook** sing versikan hook ing repo lan instal kanggo kabeh.

Bangkung, mangsuli yen hook **bisa diobati** (`--no-verify`) teges dheweke ngawungake umpan balik *lokal* kanthi cepet nanging **CI uga kudu paksane** pemeriksaan minangka jaringan keamanan asli — wawasan kunci babagan pertahanan njaba siji (hook lokal kanggo kacepetan, CI kanggo paksane).
/** ngandika otomasi pemeriksaan kualitas lan aksi workflow nambah kualitas kode lan konsistensi, lan ngandika Git hook (utamane pre-commit kanggo pemeriksaan lokal, diatur via alat lan ditambahi karo CI) minangka mekanisme luwih-digunakake kanggo iki, mangsuli Git hook — apa dheweke, panggunaan umum, manajemen tim karo alat, lan hubungan dheweke karo CI — minangka pengetahuan tingkat senior sing berharga kanggo nggawe workflow pengembangan kanthi otomasi, fokus-kualitas, cerminan praktik digunakake kanggo njaga kualitas ing tim profesional.