aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBenjamin C Meyer <ben@meyerhome.net>2010-06-19 13:54:02 -0400
committerBenjamin C Meyer <ben@meyerhome.net>2010-06-19 13:54:02 -0400
commit536997d6d30467e2e9e401cca2cf6e7daa499665 (patch)
treebf1713bc2441cd449e569a243b174258fc440d7c
parentc07c99d6178d02e910c52760f8d022e24ac2c9ca (diff)
downloadgit-hooks-536997d6d30467e2e9e401cca2cf6e7daa499665.tar.gz
git-hooks-536997d6d30467e2e9e401cca2cf6e7daa499665.tar.bz2
Mention the envvar GIT_HOOKS_VERBOSE to help debug hooks that exit with non-zero, but don't output an error
Signed-off-by: Benjamin C Meyer <ben@meyerhome.net>
-rw-r--r--README6
1 files changed, 6 insertions, 0 deletions
diff --git a/README b/README
index dbd0573..3cd593d 100644
--- a/README
+++ b/README
@@ -53,3 +53,9 @@ git_hooks/pre-commit/bsd
When you run 'git hooks' with no arguments it will list all of the hooks installed on the system. It will run the hooks with the --about argument to generate the description that is shown. Checkout the hooks in contrib for some examples.
+************************************
+Debugging
+
+When GIT_HOOKS_VERBOSE is set git-hooks will output each hook as it is run so you can trouble shoot hooks that don't report errors, but exit with non-zero.
+
+GIT_HOOKS_VERBOSE=1 git commit