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

commit-msg hook possible bad behavior with -F <file>

From
SRSeth Raymond <seth.c.raymond@gmail.com>
Date
Dec 18, 2017, 16:43 UTC
Message-ID
<CAJ4+5mHMD+yW1ZDD6KJSnMtyygLUGiHzNPgPDZUi7+KUvOczkg@mail.gmail.com>

If a commit is invoked with -F <file>, indicating that the commit message should be read from an existing file, the the prepare-commit-msg and commit-msg hooks do not operate on <file>. The first argument to the hook is always <git_repo>/COMMIT_EDITMSG, rather than <file>.

Am I wrong in this line of thinking?
-Seth
Next: Eric Sunshine
Message 1 of 3 in “commit-msg hook possible bad behavior with -F <file>”
  1. Seth RaymondDec 18, 2017
  2. Eric SunshineDec 18, 2017
  3. Seth RaymondDec 18, 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.