Say it like this
- Write a clear commit message
- Your commit message needs to be more descriptive
- I always include the ticket number in my commit message
Use it at work
In a code review
- Could you write a clearer commit message? "Fix" isn't enough.
- Please add the ticket number to the commit message.
Writing one
- Fix login timeout on slow networks
- Add retry to payment webhook handler
Team rules
- We use the imperative mood: "Add", not "Added".
- Keep the first line under 50 characters.
Don't say this
Commit message is a noun, not a verb. You commit code, you do not commit message it.
Practice
Try it
4 quick exercises
1. You need to _______ before pushing your code to the repository.
2. Which sentence uses 'commit message' incorrectly?
3. Your team is discussing best practices. How would you say this naturally?
4. Rewrite this using 'commit message': 'The text that explains what you changed in your code is very important for other people to understand.'
Say it out loud
Phrase 1 of 3
"Write a clear commit message"
We don't save your recording. The word check uses your browser's speech recognition.
More about commit message
Real examples(3)
- in a code review
"The commit message says 'Fix bug' but we need more details about which bug and how you fixed it."
- in a standup
"I pushed three commits yesterday with commit messages explaining each database optimization."
- in a team meeting
"We should establish a standard format for commit messages so the git history is easier to read."
More mistakes(2)
Handle with care. Often used as a verb incorrectly (you do not commit message something). The verb phrase is commit code or make a commit. A commit message is only the text description accompanying a commit.
- ✕Fix stuff✓Fix null pointer exception in user profile loader
Commit messages should be specific and descriptive, not vague. Future developers need to understand what actually changed.
- ✕My commit message was too long so I skipped writing one.✓I wrote a concise commit message that explains the main change.
Every commit should have a meaningful message. A short message is fine; skipping it makes history unclear.
Other forms(2)
- commit message noun
"Please write a descriptive commit message for this pull request."
- commit message history noun phrase
"The commit message history shows this feature was added three months ago."
Often used with(5)
- write a commit message · The most common action; you write or compose a commit message.
- clear commit message · A commit message should be clear and easy to understand.
- descriptive commit message · Good commit messages are descriptive and provide context.
- commit message template · Teams often use a template to standardize commit message format.
- commit message format · Different projects may have different commit message formats or conventions.
Similar words(2)
- commit description · Less common; refers to the same thing but emphasizes the explanatory aspect.
- change log entry · Broader term; a commit message is one type of change log entry.
Questions(5)
- What is a commit message and why is it important?
- A commit message is a text description of the changes you made in a code commit. It is important because it helps other developers (and your future self) understand what changed and why. Good commit messages make code reviews faster, debugging easier, and project history clearer.
- How do I write a good commit message?
- A good commit message should be concise but descriptive. Use the present tense (Fix bug, not Fixed bug), be specific about what changed, and explain why if the reason is not obvious. For example: 'Add user authentication timeout' or 'Fix memory leak in event listener cleanup.' Many teams follow conventions like starting with a verb or including a ticket number.
- Is 'commit message' a verb or noun?
- Commit message is a noun. You write a commit message or create a commit message. You do not commit message something. The verb is commit (He committed the code), and the message is the text that accompanies it.
- Can I change a commit message after I have committed?
- Yes, if you have not yet pushed to a shared repository, you can use git commit --amend to change the most recent commit message. However, you should avoid changing commit messages after pushing to shared branches, as it can confuse team members.
- What is the difference between a commit message and a pull request description?
- A commit message explains individual code changes and appears in git history. A pull request description provides a higher-level overview of all changes in that pull request and is used for code review discussions. Both are important for code quality and team communication.
