Skip to content

Commit b8c0b21

Browse files
dschogitster
authored andcommitted
rebase -i: clarify what happens on a failed exec
We had not documented previously what happens when an `exec` command in an interactive rebase fails. Now we do. Signed-off-by: Johannes Schindelin <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent 34b4731 commit b8c0b21

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

Documentation/git-rebase.txt

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -420,7 +420,8 @@ idea unless you know what you are doing (see BUGS below).
420420
--exec <cmd>::
421421
Append "exec <cmd>" after each line creating a commit in the
422422
final history. <cmd> will be interpreted as one or more shell
423-
commands.
423+
commands. Any command that fails will interrupt the rebase,
424+
with exit code 1.
424425
+
425426
You may execute several commands by either using one instance of `--exec`
426427
with several commands:

0 commit comments

Comments
 (0)