Writing good commit messages in Git - Cheat Sheet & Quick Revision

Recall & Review

beginner

Why is it important to write good commit messages?

Good commit messages help your team understand what changes were made and why. They make it easier to track history, find bugs, and collaborate effectively.

beginner

What are the three main parts of a good commit message?

A good commit message has: 1) A short summary (about 50 characters), 2) A blank line, 3) A detailed explanation if needed (wrapped at 72 characters).

beginner

What tense should you use in the commit message summary?

Use the present tense, like "Fix bug" or "Add feature", because the commit describes what the change does now.

beginner

Example of a good commit message summary?

Fix login error when password is empty

beginner

What should you avoid in commit messages?

Avoid vague messages like "fix" or "update" without details. Also avoid very long summaries or no explanation when the change is complex.

What is the recommended maximum length for the commit message summary line?

A 72 characters

B 50 characters

C 100 characters

D 120 characters

The summary line should be about 50 characters to keep it concise and readable.

Which tense is best to use in commit message summaries?

A Past tense (e.g., Fixed bug)

B Future tense (e.g., Will fix bug)

C Any tense is fine

D Present tense (e.g., Fix bug)

Present tense is preferred because the commit message describes what the change does now.

What should you do after the summary line in a commit message?

A Add a blank line

B Start writing the detailed explanation immediately

C Add a list of changed files

D Write the author name

A blank line after the summary separates it from the detailed explanation.

Why avoid vague commit messages like "fix" or "update"?

A They don't explain what was fixed or updated

B They are too short

C They are not allowed by git

D They cause merge conflicts

Vague messages don't help others understand the purpose of the change.

How should long explanations in commit messages be formatted?

A One long paragraph without breaks

B In uppercase letters

C Wrapped at 72 characters per line

D In bullet points only

Wrapping at 72 characters improves readability in many tools.

Describe the structure and style of a good commit message.

Think about how to make your message clear and easy to read.

Explain why vague commit messages are problematic and how to improve them.

Imagine your teammate reading your commit weeks later.