Ben Boeckel authored 12 years ago and Brad King committed 12 years ago

When using "git commit --amend" to edit a merge commit message the
MERGE_HEAD is long gone.  Also, some Git versions remove this file
before the commit-msg hook is called.  In either case we should still
allow long summary lines that start in 'Merge ' just as we do for
'Revert '.

Read from the project ".hooks-config" a configuration value

 hooks.start.commit-msg
 hooks.start.pre-commit
 hooks.start.prepare-commit-msg

to run from our respective hook before its main checks.

Remove hooks-chain.bash and place its content in hooks-config.bash.

Chuck Atkins authored 12 years ago and Brad King committed 12 years ago

Some hooks were getting referenced directly via $GIT_DIR/hooks while at
other times getting referenced relative via ${BASH_SOURCE%/*}.  By making
all references relative then these hooks can reside in a different folder
and still be daisy-chained by other hooks.

Although it seems reasonable to expect GIT_DIR to be set when
hooks are invoked, the "git help hooks" documentation does not
guarantee it.  On msysGit 1.7.8 (and perhaps others) "git gui"
runs prepare-commit-msg without setting GIT_DIR.  Set GIT_DIR
at the beginning of each commit hook if it is not already set.

Look for a ".hooks-config.bash" file at the top of the work tree.
Load it in each hook to get per-project configuration.  Currently
we do not define any config options, but this adds the framework.

Once our temporary COMMIT_MSG file has been removed do not advise the
author to use the file to continue editing the message.

Gerrit recognizes the Change-Id line only if it appears in the footer.

Revert commits always have longer first lines than the commit they
revert.  Do not reject those that happen to go over the threshold.  It
is much simpler if the "git revert" command creates the commit without
error.

Chain the pre-commit, commit-msg, and prepare-commit-msg hooks to
locally configured scripts.  Interpret relative paths with respect to
the working directory where the hooks run (top of work tree).  This
allows project setup scripts to add project-specific checks for each of
these hooks.

Merge commits can have long subject lines because they name other
branches.  Accept such messages as a special case for merge commits.

Add a Gerrit Change-Id header if hooks.GerritId is true.  Print help if
the option is not set and a remote URL looks like Gerrit.

Gaëtan Lehmann authored 14 years ago and Brad King committed 14 years ago

On Solaris, where /bin/sh is actually sh, not bash, some expressions
like $() are not supported.  Git's own scripts on this machine are
configured to use "#!/bin/bash".  Change our shebang line to

  #!/usr/bin/env bash

which should work almost everywhere.

Stop processing the commit message text at a "diff --git" line.  Such
lines occur when the user commits with the "-v" option.  We should not
check the patch content; it will be stripped by Git anyway.

Store a backup copy of the input message.  Remove the backup only on
success.  On failure, tell the user how to use and edit the message
without having to enter it from scratch.

These hooks perform some basic commit-time checks to keep history clean.