Re: Unable to coax hooks into working

From: Jacob Helwig <jacob.helwig@gmail.com>
Date: Apr 26, 2010, 18:11 UTC
Message-ID: <v2u8c9a061004261111l429b0c8cs73cf7e1afea3d39f@mail.gmail.com>
In-Reply-To: <B65E8227-B3C0-4AB8-A225-4A5661523CAD@pelagicore.com>

On Mon, Apr 26, 2010 at 11:04, Jeremiah Foster <jeremiah.foster@pelagicore.com> wrote:

Show 17 quoted lines

>
>
>>>      We're using debian testing and git 1.7.0.2 with the http-smart backend.
>>>
>>>      What should I do to get hooks working?
>>
>> Use the right hook.
>>
> I followed that document I listed explicitly. After lining up the right command, the right hook, and the right location, including correct executable bits as well as script ownership, a functioning script was built. Yet when the corresponding git command was called, the command failed to send data to the client which leads me to believe that the hooks wasn't called.
>
> Here is so more information on the http backend I was referring to: progit.org/2010/03/04/smart-http.html
> And the manual page: www.kernel.org/pub/software/scm/git/docs/git-http-backend.html
>
> Can I confirm that hooks work with this type of transport?
>
> Jeremiah
>

The real problem is that you're using a post-commit hook (or at least everything you said in your original email implies you are). post-commit hooks are only triggered in your _local_ repository, since this is the only place you actually commit. Doesn't matter which transport you're using, post-commit will never be triggered by a push.

You want one of the receive, or update hooks, if you're putting this in a central place, where it needs to be triggered by someone doing a push in to the repo.