summaryrefslogtreecommitdiff
path: root/t/t7504-commit-msg-hook.sh
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2017-03-23 16:07:17 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-03-27 20:55:13 (GMT)
commitb92ff6e81429c6a2636b4d6d26ab9ce5d4890fe8 (patch)
treecd8f3b4c98c4a8609eeebb7639688aceb7be8735 /t/t7504-commit-msg-hook.sh
parent789b3effec89e6f336726de109eb8be9dc60b7a5 (diff)
downloadgit-b92ff6e81429c6a2636b4d6d26ab9ce5d4890fe8.zip
git-b92ff6e81429c6a2636b4d6d26ab9ce5d4890fe8.tar.gz
git-b92ff6e81429c6a2636b4d6d26ab9ce5d4890fe8.tar.bz2
sequencer: allow the commit-msg hooks to run during a `reword`
The `reword` command used to call `git commit` in a manner that asks for the prepare-commit-msg and commit-msg hooks to do their thing. Converting that part of the interactive rebase to C code introduced the regression where those hooks were no longer run. Let's fix this. Note: the flag is called `VERIFY_MSG` instead of the more intuitive `RUN_COMMIT_MSG_HOOKS` to indicate that the flag suppresses the `--no-verify` flag (which may do other things in the future in addition to suppressing the commit message hooks, too). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t7504-commit-msg-hook.sh')
-rwxr-xr-xt/t7504-commit-msg-hook.sh2
1 files changed, 1 insertions, 1 deletions
diff --git a/t/t7504-commit-msg-hook.sh b/t/t7504-commit-msg-hook.sh
index c3d9ab0..88d4cda 100755
--- a/t/t7504-commit-msg-hook.sh
+++ b/t/t7504-commit-msg-hook.sh
@@ -230,7 +230,7 @@ chmod +x reword-editor
REWORD_EDITOR="$(pwd)/reword-editor"
export REWORD_EDITOR
-test_expect_failure 'hook is called for reword during `rebase -i`' '
+test_expect_success 'hook is called for reword during `rebase -i`' '
GIT_SEQUENCE_EDITOR="\"$REWORD_EDITOR\"" git rebase -i HEAD^ &&
commit_msg_is "new message"