Question 1

How to write a good Git commit message?

Accepted Answer

Use imperative form for the subject, keep it under 50 characters, and explain the 'why' in the body with details. The guide provides examples like 'Add use method to Credit model' and templates from Tim Pope.

Question 2

What is the 50/72 rule in commit messages?

Accepted Answer

It's a readability guideline: limit the commit subject line to 50 characters and body lines to 72 characters. This ensures messages display well in tools like Git log and email clients, as referenced from the Pro Git Book.

Question 3

Rebase vs merge: which one should I use?

Accepted Answer

Rebase creates a linear history by applying commits on top of a base branch, ideal for clean histories, while merge uses a merge commit for integrating branches, better for shared work. The guide summarizes Atlassian's tutorial, recommending rebase for local branches and merge for public ones.

Question 4

How to squash commits in Git?

Accepted Answer

Use `git rebase -i` to interactively squash multiple commits into one, or `git commit --fixup` for easier cleanup. The guide explains this with examples from the 'Rebase vs Merge' section and practical command references.

Question 5

Why use imperative form in commit messages?

Accepted Answer

Imperative form describes what the change does (e.g., 'Fix bug'), not what was done (e.g., 'Fixed bug'), aligning with how commits are applied in Git. The guide emphasizes this with good vs. bad examples to clarify the reasoning.

Question 6

Commit Messages Guide vs Conventional Commits: which is better?

Accepted Answer

This guide focuses on general best practices and education with multilingual support, while Conventional Commits is a specification with a structured format (e.g., feat:, fix:). Choose this guide for learning principles; use Conventional Commits for automated tooling integration.

Question 7

How to sign off commits with GPG for open source?

Accepted Answer

Use `git commit -s` to add a Signed-off-by line and set up GPG keys for verification. The guide references GitHub documentation and explains steps for using real names and tools like pinentry for security, as per DCO requirements.

Commit messages guide

What is Commit messages guide?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions