From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jeremiah Foster <jeremiah.foster@pelagicore.com>
Cc: git@vger.kernel.org
Subject: Re: Unable to coax hooks into working
Date: Mon, 26 Apr 2010 14:55:17 +0200 [thread overview]
Message-ID: <4BD58D35.1010307@drmicha.warpmail.net> (raw)
In-Reply-To: <4C764DDD-420E-40C6-9848-96E2197BE70D@pelagicore.com>
Jeremiah Foster venit, vidit, dixit 26.04.2010 14:32:
> Hello,
>
> After reading this page: http://book.git-scm.com/5_git_hooks.html on git hooks and doing a test implementation, I cannot seem to coax my git hooks into working.
>
> My understanding is that the hook is in the right location, in the git repository on the remote server, when doing a hook based on a post-commit update. I have down chown and chmod, the code executes, it just doesn't execute when I update the git repo and push. I have also tested this on the local machine with a different hook for the client also without success.
>
> 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.
Unsurprisingly, the post-commit hook is executed after a commit. That
should give you an indication that the hook should be in the repo where
you commit. Reading the page you linked to confirms this guess. I
refrain from comments related to the "smart backend" ;)
Michael
next prev parent reply other threads:[~2010-04-26 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 12:32 Unable to coax hooks into working Jeremiah Foster
2010-04-26 12:55 ` Michael J Gruber [this message]
2010-04-26 17:59 ` Jeremiah Foster
-- strict thread matches above, loose matches on Subject: below --
2010-04-26 18:04 Jeremiah Foster
2010-04-26 18:11 ` Jacob Helwig
2010-04-27 8:33 ` Jeremiah Foster
2010-04-27 8:52 ` Michael J Gruber
2010-04-27 9:08 ` Jeremiah Foster
2010-04-27 10:47 ` Michael J Gruber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BD58D35.1010307@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=jeremiah.foster@pelagicore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.