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
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.
✅ 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
