docs: document core.hooksPath=/dev/null
If a user wishes to disable hooks, then they can do so using the established pattern of setting 'core.hooksPath' to /dev/null. This is already tested in t1350-config-hooks-path.sh, but has not previously been visible in the documentation. Update the documentation to include this as an option. Signed-off-by: Derrick Stolee <stolee@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>maint
parent
683c54c999
commit
1b2eee94f1
|
|
@ -512,6 +512,11 @@ centrally configure your Git hooks instead of configuring them on a
|
||||||
per-repository basis, or as a more flexible and centralized
|
per-repository basis, or as a more flexible and centralized
|
||||||
alternative to having an `init.templateDir` where you've changed
|
alternative to having an `init.templateDir` where you've changed
|
||||||
default hooks.
|
default hooks.
|
||||||
|
+
|
||||||
|
You can also disable all hooks entirely by setting `core.hooksPath`
|
||||||
|
to `/dev/null`. This is usually only advisable for expert users and
|
||||||
|
on a per-command basis using configuration parameters of the form
|
||||||
|
`git -c core.hooksPath=/dev/null ...`.
|
||||||
|
|
||||||
core.editor::
|
core.editor::
|
||||||
Commands such as `commit` and `tag` that let you edit
|
Commands such as `commit` and `tag` that let you edit
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue