Skip to content

Commit d4d262d

Browse files
committed
Merge branch 'sb/merge-commit-msg-hook'
As "git commit" to conclude a conflicted "git merge" honors the commit-msg hook, "git merge" that records a merge commit that cleanly auto-merges should, but it didn't. * sb/merge-commit-msg-hook (2017-09-22) 1 commit (merged to 'next' on 2017-09-25 at 096e050) + Documentation/githooks: mention merge in commit-msg hook Add documentation for a topic that has recently graduated to the 'master' branch. * sb/merge-commit-msg-hook: Documentation/githooks: mention merge in commit-msg hook
2 parents 8096e1d + ce82edd commit d4d262d

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

Documentation/githooks.txt

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -127,11 +127,10 @@ help message found in the commented portion of the commit template.
127127
commit-msg
128128
~~~~~~~~~~
129129

130-
This hook is invoked by 'git commit', and can be bypassed
131-
with the `--no-verify` option. It takes a single parameter, the
132-
name of the file that holds the proposed commit log message.
133-
Exiting with a non-zero status causes the 'git commit' to
134-
abort.
130+
This hook is invoked by 'git commit' and 'git merge', and can be
131+
bypassed with the `--no-verify` option. It takes a single parameter,
132+
the name of the file that holds the proposed commit log message.
133+
Exiting with a non-zero status causes the command to abort.
135134

136135
The hook is allowed to edit the message file in place, and can be used
137136
to normalize the message into some project standard format. It

0 commit comments

Comments
 (0)