commit does not always succeed, so we'll have to check for it in the absence of set -e. This fixes a regression introduced in 9e4bc7dd1bb9d92491c475cec55147fa0b3f954d
Signed-off-by: Eric Wong <normalperson@yhbt.net> --- git-rebase.sh | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-)
Show changes to git-rebase.sh +6 −1
diff --git a/git-rebase.sh b/git-rebase.sh index 9ad1c44..28860fc 100755 --- a/git-rebase.sh +++ b/git-rebase.sh @@ -59,8 +59,13 @@ continue_merge () { if test -n "`git-diff-index HEAD`" then + if ! git-commit -C "`cat $dotest/current`" + then + echo "Commit failed, please do not call \"git commit\"" + echo "directly, but instead do one of the following: " + die "$RESOLVEMSG" + fi printf "Committed: %0${prec}d" $msgnum - git-commit -C "`cat $dotest/current`" else printf "Already applied: %0${prec}d" $msgnum fi
-- 1.4.1.rc1.gc7c5