Apa sing ndadekake commit lan pesan commit sing apik?

Question

Accepted Answer

Commit sing apik yaiku **fokus** (siji pangubahan logis) kanthi **pesan sing jelas** sing nerangake apa sing owah lan dene apa. Commit lan pesan sing dirancang kanthi apik nggawe sajarah proyek bisa diwaca, migunani kanggo ngerti pangubahan, debugging, lan kolaborasi.

## Pesan commit sing apik

```text
GOOD message structure:
  Short summary line (~50 chars, imperative mood, capitalized, no period)
  <blank line>
  Optional body: explain WHAT and WHY (not how — the code shows how),
  wrap at ~72 chars. Reference issues if relevant.
```

```text
✅ GOOD:
  Add user email validation to registration form

Validate email format before submission to prevent invalid
  accounts. Fixes #142.

❌ BAD:
  "fixed stuff", "update", "asdf", "changes", "wip"
  → vague, uninformative — useless when reviewing history later
```

## Konvensyon imperative mood

```text
Write the summary as a COMMAND/instruction (imperative):
  ✓ "Add feature", "Fix bug", "Update docs", "Remove dead code"
  ✗ "Added feature", "Fixes bug", "Updating docs"
→ Convention: it reads as "this commit will [Add feature]" (matches Git's own messages).
```

## Commit sing apik: atomic lan fokus

```text
✓ ATOMIC — each commit is ONE logical change (not many unrelated changes lumped together)
✓ Focused — "Add login" and "Fix typo" are SEPARATE commits, not one
✓ Working — ideally each commit leaves the code in a working state
Why: focused commits are easier to REVIEW, REVERT (undo one change cleanly),
  understand, and bisect (find which commit introduced a bug).
```

## Conventional Commits (standar populer)

```text
type(scope): description    → feat: add login | fix: handle null | docs: update README
  types: feat, fix, docs, refactor, test, chore, etc.
→ Enables automated changelogs/versioning; widely adopted in many projects.
```

## Dene penting

Nanggap apa sing ndadekake commit lan pesan commit sing apik yaiku berharga kanggo **nggawe sajarah proyek sing bisa diwaca lan migunani**, dadi iku pengetahuan praktis penting sing signifikan pengaruhe ing kolaborasi lan keberlanjutan. **Pesan commit sing apik** penting amarga sajarah commit yaiku wujud dokumentasi krusial — pesan sing jelas (ringkesan singkat nerangake *apa* sing owah, kanthi badan nerangake *dene* manawa perlu) ndadekake bisa ngerti carane lan dene kode berkembang, iki berharga banget nalika ngatonake sajarah, debugging (ngerti dene pangubahan digawe), utawa onboarding.

Pesan sing ora jelas ("diperbaiki barang", "update", "wip") ndadekake sajarah ora migunani, ndadekake impossible ngerti pangubahan mengko — iki biaya nyata.

Konvensyon **imperative mood** ("Add feature" ora "Added feature") yaiku standar luwih-dileksoni lahir ngerti. **Commit sing apik yaiku atomic lan fokus** (saben commit siji pangubahan logis, ora akeh pangubahan ora ana sambunge digawe bareng) yaiku penting sama: commit fokus luwih gampang **ditintingi** (pereview ngerti siji pangubahan), **dibalikan** (mbatalake siji pangubahan kanthi bersih tanpa pengaruh liya), ngerti, lan **bisect** (nandang commit nggawe bug) — dadi struktur commit langsung pengaruhe carane sajarah migunani kanggo debugging lan kolaborasi.

Naggak Conventional Commits (standar `type(scope): description` ndadekake otomatis changelog lan versioning) berharga amarga ndunia adopsi.

Samono sajarah commit yaiku dokumentasi penting lan commit/pesan sing apik ndadekake bisa diwaca lan migunani (kanggo ngerti, ninjau, debugging, lan kolaborasi) dene sing ala ndadekake ora migunani, lan samono ngomposisi commit fokus kanthi pesan jelas yaiku tanda praktek Git profesional, nangerteni apa sing ndadekake commit lan pesan commit sing apik yaiku berharga, pengetahuan praksis relevan kanggo kolaborasi efektif lan sajarah keberlanjutan — katrampilan sing membedake developer sing penuh pertimbangan lan bermakna ningkatke jangka panjang usability lan workflow tim proyek.