The argument of the 'update-ref' instruction is treated as a fully qualified ref, and there is no DWIMery to interpret 'update-ref feature' to create/update the branch named "feature", i.e. the ref "refs/heads/feature". Update the help text appended to the todo list to make this clearer. Signed-off-by: SZEDER Gábor <szeder.dev@xxxxxxxxx> --- rebase-interactive.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/rebase-interactive.c b/rebase-interactive.c index 7407c59319..7c6288f997 100644 --- a/rebase-interactive.c +++ b/rebase-interactive.c @@ -57,9 +57,9 @@ void append_todo_help(int command_count, " create a merge commit using the original merge commit's\n" " message (or the oneline, if no original merge commit was\n" " specified); use -c <commit> to reword the commit message\n" -"u, update-ref <ref> = track a placeholder for the <ref> to be updated\n" -" to this position in the new commits. The <ref> is\n" -" updated at the end of the rebase\n" +"u, update-ref <ref> = track a placeholder for the fully-qualified <ref> to\n" +" be updated to this position in the new commits. The\n" +" <ref> is updated at the end of the rebase\n" "\n" "These lines can be re-ordered; they are executed from top to bottom.\n"); unsigned edit_todo = !(shortrevisions && shortonto); -- 2.38.0.rc2.542.g9b62912f7f
