Eugene Sajine <euguess@xxxxxxxxx> writes:
> For example, so i could say
> $ git config --global hooks.dir ~/git/hooks
I don't think "global" hooks are useful for people who work on more than
one project, or people who interact in more than one ways to projects.
Different projects typically have different needs out of the hooks
(e.g. pre-commit policy), and different workflows typically call for
different needs out of the hooks (e.g. I would want to be able to rebase
in my private working repository but not in the repository I use for
integration of other people's branches).
So I am fairly negative on your particular example above.
But it is understandable for one to use more than one repository for the
same project and use them in the same way; in such a case, I agree that a
way to ensure that these repositories use the same set of hooks (and
non-hooks, e.g. commit templates, local ignore pattern files, etc.) is
desirable.
So I would imagine that your example without "--global" would be a
reasonable thing to do once per repository.
Now, as long as the "do once per repository" action that you need to do is
simple enough, it doesn't necessarily have to be "git config". Perhaps
[alias]
set-hooks = !"sh -c 'rm -fr .git/hooks && ln -s $1 .git/hooks' -"
could also be a simple single-command solution that is "do once per
repository".
Can't we do better and make this "do nunce per repository" instead?
You first have to think how you are creating these more-than-one
repositories you would want to make sure they use the same hooks. For
example, do you have a single "upstream" repository and everything is a
clone of it? If so, perhaps a way to tell "clone" via $HOME/.gitconfig
that when cloning from a particular URL you would want to run a particular
post-clone script might be a better way.
--
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