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

Best practices/conventions for tags and references in commit message

From
TKThomas Koch <thomas@koch.ro>
Date
May 27, 2014, 11:26 UTC
Message-ID
<201405271326.36031.thomas@koch.ro>
Hi,

different projects or tools have conventions to include machine parsable information in commit messages, e.g.:

Closes: #42
Thanks: my mother, my wife
Git-Dch: Ignore
Commit-Id: 50M3R34LLYR4ND0MB1TSANDNUMB3R5

(see thread: "RFE: support change-id generation natively" for Commit-Id) ("Git-Dch: Ignore" ecludes the commit from the changelog)

Are you aware of any convention or best practices for such tags that are used in more than one project? Are there more tags like these?

Maybe it would also be helpful to have some more plumbing support from Git for such tags. But I've not yet thought enough about this.

Best regards, Thomas Koch
Next: Johan Herland
Message 1 of 4 in “Best practices/conventions for tags and references in commit message”
  1. Thomas KochMay 27, 2014
  2. Johan HerlandMay 27, 2014
  3. Thomas KochJun 5, 2014
  4. Christian CouderJun 5, 2014

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.