Eric Sunshine <sunshine@xxxxxxxxxxxxxx> writes:
>> Which may be something we would want to have a test for, though.
>
> Good idea. How about the following as a squash-in?
Sounds sensible.
At this point we do not have "worktree list", but if we gained that,
we may want to add this as one more postcondition after the failed
"worktree add":
git worktree list >actual &&
! grep precious actual
but that should happen in the series that adds "worktree list" ;-)
> --- 8< ---
> From: Eric Sunshine <sunshine@xxxxxxxxxxxxxx>
> Subject: [PATCH] fixup! worktree: add: auto-vivify new branch when <branch> is omitted
>
> ---
> t/t2025-worktree-add.sh | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/t/t2025-worktree-add.sh b/t/t2025-worktree-add.sh
> index 8fe242f..ead8aa2 100755
> --- a/t/t2025-worktree-add.sh
> +++ b/t/t2025-worktree-add.sh
> @@ -150,4 +150,13 @@ test_expect_success '"add" with <branch> omitted' '
> test_cmp_rev HEAD bat
> '
>
> +test_expect_success '"add" auto-vivify does not clobber existing branch' '
> + test_commit c1 &&
> + test_commit c2 &&
> + git branch precious HEAD~1 &&
> + test_must_fail git worktree add precious &&
> + test_cmp_rev HEAD~1 precious &&
> + test_path_is_missing precious
> +'
> +
> test_done
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html