How to Write a Git Commit Message


124 bookmarks. First posted by loki february 2017.


There are well-established conventions as to what makes an idiomatic Git commit message.
sw  dev  git  tips 
21 days ago by Volgar
If you browse the log of any random Git repository, you will probably find its commit messages are more or less a mess.
git  best-practices  development 
8 weeks ago by scottkillen
If you browse the log of any random Git repository, you will probably find its commit messages are more or less a mess. For example, take a look at from my early days committing to Spring: Which would you rather read?
git  dev 
8 weeks ago by mayrav
Commit messages that can complete the sentence "If applied, this commit will.." is encouraged
git  coding 
june 2017 by scottnelle
A properly formed Git commit subject line should always be able to complete the following sentence:

If applied, this commit will your subject line here
june 2017 by tullyhansen
What it says. Summarises and argues for these 7 principles for good commit messages:
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how

Includes several references to other similar articles.
revision_control  git 
june 2017 by stu-rem
If you browse the log of any random Git repository, you will probably find its commit messages are more or less a mess. For example, take a look at from my early days committing to Spring: Which would you rather read? via Pocket
june 2017 by billchristian
The seven rules of a great Git commit message

Keep in mind: This has all been said before.

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how

https://web.archive.org/web/20170606073413/https://chris.beams.io/posts/git-commit/
https://archive.is/Fn3MI

References
http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
https://www.git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project#_commit_guidelines
https://github.com/torvalds/subsurface-for-dirk/blob/master/README#L92-L120
http://who-t.blogspot.co.at/2009/12/on-commit-messages.html
https://github.com/erlang/otp/wiki/writing-good-commit-messages
https://github.com/spring-projects/spring-framework/blob/30bce7/CONTRIBUTING.md#format-commit-messages
git  commit  language 
june 2017 by coffeebucket
How to Write a Git Commit Message - Added September 13, 2015 at 11:55PM
git 
may 2017 by xenocid
In this post, Chris Beams addresses the most basic element of keeping a healthy commit history: how to write an individual commit message.
development  git  documentation 
april 2017 by billglover
Fortunately, there are well-established conventions as to what makes an idiomatic Git commit message. Indeed, many of them are assumed in the way certain Git commands function. There’s nothing you need to re-invent. Just follow these seven rules and you’re on your way to committing like a pro.
git  commit  message  guideline  style  writing 
april 2017 by rbardini
How to Write a Git Commit Message
git 
march 2017 by jpalat
How to Write a Git Commit Message via Instapaper http://ift.tt/2mjeue7
IFTTT  Instapaper 
march 2017 by chaoxian