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

Re: post-checkout hook not run on clone

From
Llayer <layer@known.net>
Date
Mar 3, 2009, 05:02 UTC
Message-ID
<23978.1236056549@relay.known.net>
In-Reply-To
<20090303042848.GC18136@coredump.intra.peff.net>
Jeff King <peff@peff.net> wrote:
Show 8 quoted lines
>> On Mon, Mar 02, 2009 at 02:43:37PM -0800, layer wrote:
>> 
>> > I realize this might be a feature, but when I switch to the master
>> > branch with "git checkout master" it is, and I would think that a
>> > clone that gets the master branch would also does a sort of "checkout
>> > master" and would run the hook.
>> 
>> Right. Hooks are not cloned with the repo.

The hook in question was in /usr/share/git-core/templates/hooks/, so it would get setup on clone. That works fine. If I immediately switch branches, the hook gets called. It's just the `post-clone' (when I assume something like `checkout' is done), the hook doesn't get called.

>> The general wisdom on the list is that it's a bad idea to run remote
>> code arbitrarily for security reasons...

I agree, but not in this specific situation. All the users of the code are trusted, as is the author of the hooks.

Previous: Jeff KingNext: Jeff King
Message 3 of 11 in “post-checkout hook not run on clone”
  1. layerMar 2, 2009
  2. Jeff KingMar 3, 2009
  3. layerMar 3, 2009
  4. Jeff KingMar 3, 2009
  5. clone: run post-checkout hook when checking outJeff King, Mar 3, 2009
  6. Junio C HamanoMar 3, 2009
  7. Jay SoffianMar 3, 2009
  8. Nanako ShiraishiMar 3, 2009
  9. Jeff KingMar 3, 2009
  10. layerMar 4, 2009
  11. Shawn O. PearceMar 3, 2009

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.