Git hooks menene kuma ana amfani da su ta yaya?

Question

Accepted Answer

**Git hooks** sunan rubuce-rubuce ne da Git ke gudana **ta atomatik** a wasu wurare na Git workflow (kafin/bayan commits, pushes, merges, da sauransu). Suna ba da damar sarrafa aiki — karfafawa daidaita, gudana jajjerori, da kuma fara ayyuka — kuma an fi amfani da su don ingancin kodoro da haɗi da CI.

## Menene hooks

```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
```

## Amfani da aka sani

```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
```

## Shawarwaewa hooks a gida

```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).
```

## Menene mahalarta

Sanin Git hooks yana da muhimmanci ga ilimin matakin da ke saman gida don **sarrafa aiki na jajjerori inganci da ayyukan workflow**, don haka yana da amfani don kiyaye ingancin kodoro da haɗi da CI/CD.

Hooks suna ba da damar **sarrafa aiki a abubuwa muhimmanci na Git** — gudana rubuce-rubuce ta atomatik kafin/bayan commits, pushes, merges, da sauransu — wanda aka fi amfani da shi don karfafawa daidaita da kama matsaloli da wuri.

Amfani da ya fi dacewa kuma mabuchi shine **hook kafin-commit** don gudana **linting, daidaita tsari, gwaje gyarte, da gano siri kafin a xi commit** — ba da sauri jaka da tabbatar da jiya daidai ta atomatik (don haka matsaloli a gama da su a lokacin commit maimakon jiya a CI ko bada shawara), wata aiki da aka fi so.

Wasu amfani (hooks na commit-msg wajen karfafawa jajije babi kamar Conventional Commits, hooks kafin-push na gudana gwaje domin hana tin broken code, da hooks gefen server na karfafawa patapata ko kuma fara ayyukan CI/CD da deploy) suna fadada sarrafa aiki a duka workflow.

Sanin gida na **shawarwaewa gida** yana da muhimmanci: `.git/hooks/` gida ne kuma **ba a xi commit ba**, don haka hooks ba sa share ta atomatik — share su a gida yana buƙatar kayan aiki kamar **Husky, pre-commit, ko lefthook** wajen share hooks a repo kuma sanya su wa kowa.

Da mahimmanci, sanin cewa hooks **za su iya ware** (`--no-verify`) yana nufin suna ba da sauri jaka na gida kuma **CI dole ne tabbatar** jajjerori a matsananciyar amincewa — sanin muhimmanci game da kariya ta zafi (hooks gida domin sauri, CI domin karfafawa).

Don cewa sarrafa aiki na jajjerori inganci da ayyukan workflow yana haɓaka ingancin kodoro da daidaita gida, kuma don cewa Git hooks (musamman pre-commit domin gwaje gida, shawarwa ta kayan aiki kuma karantawa ta CI) sune keɓantaccen halittar wa haka, sanin Git hooks — menene su, amfani da aka sani, shawarwaewa gida ta kayan aiki, da dangantakarsu da CI — yana da muhimmanci ga ilimin matakin da ke saman gida domin gina workflow ƙare-ƙare na sarrafa aiki kuma mai arzu inganci, wanda ke nuna abubuwan amfani a shawarwari na shafarar aiki domin kiyaye inganci a ƙwararren gida.