Git & GitHub · Lesson 12 of 144
Good Commit Messages
Short, clear, and useful.
A commit message is a note to your future self, and to your team. In six months, you won't remember what you did today. The message will.

- A note to your future self
- And to your team
- You will forget, the message won't
Bad and good messages
Look at the difference. Stuff. Fix. Changes. These tell you nothing. Good messages say what the commit does, in a short sentence. Add contact form. Fix broken link on home page. Reading a list of good messages is like reading the story of the project.
Unhelpful
- stuff
- fix
- changes
Helpful
- Add contact form
- Fix broken link on home page
- Remove old logo
Simple rules
Here are four simple rules. Start with a verb, like add, fix, or remove. Keep it short, around fifty characters. Write it like a command, add, not added. And make each commit about one thing, so the message is easy to write.
Start with a verbAdd, Fix, Remove
Keep it shortabout 50 characters
Like a commandAdd, not Added
One thingone commit
Summary
Good messages are short, start with a verb, and describe one change. Next, how to read your history.
Key takeaways- Start with a verb
- About 50 characters
- One change per commit
Next up: Reading History — git log