How to Write a Git Commit Message


196 bookmarks. First posted by loki february 2017.


A well-crafted Git commit message is the best way to communicate context about a change to fellow developers (and indeed to yourself). A diff will tell you what changed, but only the commit message can properly tell you why.
git  best-practices 
6 days ago by zxaos
via Pocket - How to Write a Git Commit Message - Added May 14, 2018 at 10:31AM
IFTTT  Pocket 
5 weeks ago by BastiRe
A well-crafted Git commit message is the best way to communicate context about a change to fellow developers, and indeed to their future selves.
git  commit  message  title  body  rebase  squash  documentation 
5 weeks ago by stuball
pplied, this commit w
programming  git 
7 weeks ago by jkb63
I should probably revisit this post on crafting good git commit messages periodically
Coding  commits  Git 
9 weeks ago by brianhoch
on git commit messages
git  productivity  collaboration 
10 weeks ago by jshwlkr
The contributors to these repositories know that a well-crafted Git commit message is the best way to communicate context about a change to fellow developers (and indeed to their future selves). A diff will tell you what changed, but only the commit message can properly tell you why.
git  devstandards  development  bestpractices 
february 2018 by mhick
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
IFTTT  Pocket  git  work 
january 2018 by judeopiston
31 Aug 2014 | revision history | | Introduction: Why good commit messages matter If you browse the log of any random Git repository, you will probably find its…
from instapaper
january 2018 by divigation
A project’s long-term success rests (among other things) on its maintainability, and a maintainer has few tools more powerful than his project’s log. It’s worth taking the time to learn how to care for one properly. What may be a hassle at first soon becomes habit, and eventually a source of pride and productivity for all involved.

In this post, I am addressing just the most basic element of keeping a healthy commit history: how to write an individual commit message. There are other important practices like commit squashing that I am not addressing here. Perhaps I’ll do that in a subsequent post.
git  logs  writing  advice 
october 2017 by brandon.w.barry
There are well-established conventions as to what makes an idiomatic Git commit message.
sw  dev  git  tips 
september 2017 by Volgar