How to bypass the post-commit hook?

--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.

-- 
Ping Yin

On Sun, Dec 30, 2007 at 23:12:12 +0800, Ping Yin wrote:

--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 [off-list ref]

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...

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

On Mon, Dec 31, 2007 at 10:50:27 +0100, Pascal Obry wrote:

Jan Hudec a écrit :

quoted

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 [off-list ref]