Courses / GitHub
12. Commit message conventions (imperative tense, concise summary)
Writing concise, descriptive commit messages and following a simple convention like imperative tense.
1 min read Chapter 12 of 32
Git / Bash
Commit message conventions (imperative tense, concise summary)
A commit message explains what a change does in one clear, imperative sentence so others (and future you) can understand history quickly.
"I want my project history to read like a changelog, not a mystery novel."
Write a short (50-char summary) imperative-line describing what the commit changes, optionally followed by a blank line and a longer body explaining why and how.
"I want my project history to read like a changelog, not a mystery novel."
Write a short (50-char summary) imperative-line describing what the commit changes, optionally followed by a blank line and a longer body explaining why and how.