Learn Git in a Day

Commit Messages That Don't Suck

While we're on the topic, let's talk about commit messages. You've been writing short, one-line messages with -m, and that's fine for simple changes. But there's a widely used convention worth knowing.

A good commit message has a short first line (50 characters or less) that summarizes the change, optionally followed by a blank line and a longer explanation. The first line should be written as an imperative - "Add feature" rather than "Added feature" or "Adding feature."

For example:

Add floor division function

Implement floor_divide(a, b) that returns a // b.
Includes a zero-division check that returns an error
message, consistent with the existing divide function.