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

Re: How to bypass the post-commit hook?

From
JHJan Hudec <bulb@ucw.cz>
Date
Jan 14, 2008, 17:59 UTC
Message-ID
<20080114175951.GA5527@efreet.light.src>
In-Reply-To
<4778BB63.6080908@obry.net>
On Mon, Dec 31, 2007 at 10:50:27 +0100, Pascal Obry wrote:
Show 6 quoted lines
> Jan Hudec a écrit :
> > By the way, what is your post-commit hook doing anyway? Modifying the work
> > tree *after* a commit does not sound like a common thing to do.
> 
> Or just trigger a build via a built robot or record a commit information
> into an issue tracker...
That's not a case of "modifying a work tree *after* a commit".

There are many valid uses for post-commit hook and this is one of them. But like the others it does not modify versioned files. That was the issue discussed (and pre-commit indeed turned out a better match).

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Pascal ObryNext: Jan Hudec
Message 4 of 9 in “How to bypass the post-commit hook?”
  1. Ping YinDec 30, 2007
  2. Jan HudecDec 30, 2007
  3. Pascal ObryDec 31, 2007
  4. Jan HudecJan 14, 2008
  5. Jan HudecDec 31, 2007
  6. Jan HudecDec 31, 2007
  7. Ping YinDec 31, 2007
  8. Jan HudecDec 31, 2007
  9. Ping YinDec 31, 2007

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.