git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to make devs write better commit messages

From
TKThomas Koch <thomas@koch.ro>
Date
Dec 7, 2011, 07:06 UTC
Message-ID
<201112070806.09539.thomas@koch.ro>
In-Reply-To
<CAOJsP-X0ZWT5HLHcBc2FmhoMpWFOvEFADiM9jGZ9R1ctqHDJ9w@mail.gmail.com>
Joseph Huttner:
> The bottom line is that good commit messages are really important, so
> we should make it as easy as possible for developers to go ahead and
> write a perfect commit message every time they commit code.

I recently started to work with the code review system Gerrit[1]. First I did not pay attention to it, but later I was amazed that the commit message can (and should) be reviewed just like the code changes.

So if you're using a code review prozess (you should!) then also include the commit message in the review.

[1] http://en.wikipedia.org/wiki/Gerrit_%28software%29
Thomas Koch, http://www.koch.ro
Previous: Hilco Wijbenga
Message 5 of 5 in “How to make devs write better commit messages”
  1. Joseph HuttnerDec 6, 2011
  2. Michael SchubertDec 6, 2011
  3. Junio C HamanoDec 7, 2011
  4. Hilco WijbengaDec 7, 2011
  5. Thomas KochDec 7, 2011

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.