diff options
| author | Junio C Hamano <gitster@pobox.com> | 2008-03-16 07:50:22 (GMT) |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2008-03-16 08:00:40 (GMT) |
| commit | e637122ef2d3911568d7d016f723cdad61730069 (patch) | |
| tree | c0532c180529194f243c129f3380a75dc74e5ae3 | |
| parent | 6bf4f1b4c9d78b2061bd5f3bf77bb21112b755be (diff) | |
| download | git-e637122ef2d3911568d7d016f723cdad61730069.zip git-e637122ef2d3911568d7d016f723cdad61730069.tar.gz git-e637122ef2d3911568d7d016f723cdad61730069.tar.bz2 | |
rebase -m: do not trigger pre-commit verification
When rebasing changes that contain issues that the pre-commit hook flags
as problematic, the rebase cannot be continued. However, rebase is about
transplanting commits that are already made with as little distortion as
possible, and pre-commit check should not interfere.
Earlier, c5b09fe (Avoid update hook during git-rebase --interactive,
2007-12-19) fixed "rebase -i", but "rebase -m" shared the same issue.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rwxr-xr-x | git-rebase.sh | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/git-rebase.sh b/git-rebase.sh index 6b9af96..bc0c1c4 100755 --- a/git-rebase.sh +++ b/git-rebase.sh @@ -63,7 +63,7 @@ continue_merge () { cmt=`cat "$dotest/current"` if ! git diff-index --quiet HEAD -- then - if ! git-commit -C "$cmt" + if ! git commit --no-verify -C "$cmt" then echo "Commit failed, please do not call \"git commit\"" echo "directly, but instead do one of the following: " |