Brian Collins <bricollins@xxxxxxxxx> writes: > Run global hooks in the directory specified by the config variable > hooks.dir before every attempt at running a local hook. If the > global hook fails, the local hook will not run. If the global hook is > absent, the local hook runs normally. It is left unspecified what happens when the global hook exists and it succeeds. Watch out for hooks that read from their standard input. In any case, the above is totally backwards from the usual practice and expectation of local things overriding the global default. If you want a site-wide policy suggestion, default templates would be a more acceptable way (and the implementation of hooks you install to developer repositories can choose to look at $GIT_DIR/hooks/local-foo-hook). By the way, with a distributed scm, anything-wide policy enforcement at the level of developer's individual working repositories is a lost cause. You are giving freedom to do anything on their own copy of the history to the developers; the project-wide policy is to be enforced at the perimeter of your authoritative repository of the project. -- 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