Re: Is there any way to make hooks part of the repository?
- From
Junio C Hamano <gitster@pobox.com>
- Date
- May 1, 2012, 21:03 UTC
- Message-ID
- <7vaa1r8vhy.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <86r4v3mxf7.fsf@red.stonehenge.com>
merlyn@stonehenge.com (Randal L. Schwartz) writes:
Show 10 quoted lines
>>>>>> "Junio" == Junio C Hamano <gitster@pobox.com> writes: > > Junio> By design. Do you want me to include "rm -fr ~hilco" in some hook of > Junio> git.git repository? > > This just came up yesterday at $PRIMARY_CLIENT. One idea we kicked > around was having a convention for storing the hooks-to-be-populated in > ".githooks" in the repository tree, and then having clone notice that > and offer to install them directly if from a trusted source, or at least > move them into a disabled state in .git/hooks otherwise.
We've talked about something like that a few times in the past, but as far as I (am concerned / remember) the conclusion has always been that is not worth "standardizing", i.e. nothing a ./setup script in-tree or a Makefile target cannot offer the same convenience.