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
Dec 30, 2007, 21:50 UTC
Message-ID
<20071230215008.GB20098@efreet.light.src>
In-Reply-To
<46dff0320712300712l78c1cdaeya5fa105be01f6b74@mail.gmail.com>
On Sun, Dec 30, 2007 at 23:12:12 +0800, Ping Yin wrote:
Show 6 quoted lines
> --no-verify can bypass pre-commit hook? Then how to bypass post-commit hook?
> 
> Usually I want post-commit take effect. However, in the middle of
> git-rebase, i want to bypass post-commit when 'git-commit --amend'
> since my post-commit hooks will modify the working directory and so
> make following rebase troubesome.

There does not seem to be an option to do it, but you can always temporarily disable it (unset the executable permission on it).

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.

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: Ping YinNext: Pascal Obry
Message 2 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.