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

Re: Git hooks are not called over HTTP

From
Shawn O. Pearce <spearce@spearce.org>
Date
Oct 17, 2008, 14:11 UTC
Message-ID
<20081017141107.GE9877@spearce.org>
In-Reply-To
<m38wsnk24l.fsf@localhost.localdomain>
Jakub Narebski <jnareb@gmail.com> wrote:
Show 10 quoted lines
> "KwangYul Seo" <kwangyul.seo@gmail.com> writes:
> 
> > I have setup a git repository with post-receive and post-update
> > enabled. I configured hooks.envelopesender and hooks.mailinglist. I
> > confirmed that it works fine with push from local repositories.
> > However, hooks are never called when push is done over HTTP.
> 
> Perhaps that would get improved when "smart" HTTP protocol gets
> implemented (currently in the phase of design, I think just after
> designing protocol).

Yes. The Git-in-HTTP protocol for push basically calls for an embedding of send-pack/receive-pack's protocol into HTTP, and implementation wise will probably be invoking git-receive-pack on the web server side of the connection. So if/when that finally gets implemented we'd run hooks over HTTP, but *ONLY* if both sides support the new Git-in-HTTP protocol.

If both sides are still using WebDAV, no hooks, for the reason you cited earlier.

-- 
Shawn.
Previous: Jakub Narebski
Message 3 of 3 in “Git hooks are not called over HTTP”
  1. KwangYul SeoOct 17, 2008
  2. Jakub NarebskiOct 17, 2008
  3. Shawn O. PearceOct 17, 2008

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.