On Wed, Aug 29, 2007 at 11:05:07AM CEST, Andy Parkins wrote: > On Tuesday 2007 August 28, Petr Baudis wrote: > > > On Tue, Aug 28, 2007 at 06:46:48PM CEST, Josh England wrote: > > > When cloning an existing repository, is there any way to grab > > > the .git/hooks files as part of the clone (or pull)? > > > > No. You can add the appropriate instructions to instructions how to > > clone the repository, users have to install the hooks manually. > > > > Now I went on with a large writeup on considerations for implementing > > such a feature (including security), but then I scrapped it. What would > > you like to use these hooks for? Really, perhaps it's best to instead do > > any "post-commit" etc. checks at the push time instead of the commit > > time, so that developers can still freely commit locally, e.g. I > > sometimes do temporary commits on side branches of various work in > > progress changes, then randomly merge them together etc. before I come > > up with the final sequence of commits that I push out. > > I've not done it for myself yet, but I had an idea about making an independent > branch in the repository itself containing the hook scripts for that project. > That way, the cloners get the scripts but still have to knowingly install > them themselves. > > If you were feeling particularly brave, you could check that branch out > in .git/hooks. Yes, that was one of my ideas as well; but one thing is that you may want different hooks scripts for different branches or even different times in a particular branch. So maybe .git-hooks/, with each change printing a bit fat warning and setting -x. On the other hand maybe it might be simpler to do the tests for which branch/commit are you working on in the hooks themselves. But overally, I'm still not convinced that there is a feasible use-case for the cloned hooks at all. Someone has a particular example? -- Petr "Pasky" Baudis Early to rise and early to bed makes a male healthy and wealthy and dead. -- James Thurber - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html