Writing Good Commit Messages: A Practical Guide
Too Long; Didn't Read A well-crafted Git commit message is the best way to communicate context about a change to other developers working on that project and indeed to your future self. There are several conventions used by several teams and developers to write good commit messages. The first line is the subject (short description), the next is the extended description (body) The first. line is a short (short) summary, and the rest of the text as an email. The body is critical (unless you omit the body entirely); tools like rebase rebase can get confused if you run the two together.