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

Requesting suggestions for a good sample "prepare-commit-msg" hook

From
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
Date
Jul 5, 2017, 16:45 UTC
Message-ID
<1499273152.16389.2.camel@gmail.com>
Hello all,

There's an attempt in progress to replace the part of the sample "prepare-commit-msg" hook that comments the "Conflicts" part of a merge commit message. This is being done as the "Conflicts" portion is commented by default for quite some time (since 2014) and thus the script in the hook is useless.

It's worth noting that it was the only part of the sample hook that *wasn't* commented by default i.e., it was the only portion of the sample hook that could be used just by enabling it by renaming the hook. So, just removing that portion of the solution wouldn't be a solution as it wouldn't be nice to have a whole sample hook to be commented for various reasons. So, we're searching for scripts that could both be helpful to users and could serve as a good sample to prove what could be done using the hooks.

In case anyone has any suggestions about what could prove to be an alternative please send them in!

-- 
Kaartic
Next: Junio C Hamano
Message 1 of 6 in “Requesting suggestions for a good sample "prepare-commit-msg" hook”
  1. Kaartic SivaraamJul 5, 2017
  2. Junio C HamanoJul 5, 2017
  3. Kaartic SivaraamJul 5, 2017
  4. Kaartic SivaraamJul 5, 2017
  5. Junio C HamanoJul 5, 2017
  6. Kaartic SivaraamJul 6, 2017

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.