From: "Yoichi NAKAYAMA via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Harald Nordgren <haraldnordgren@gmail.com>,
Yoichi Nakayama <yoichi.nakayama@gmail.com>,
"D. Ben Knoble" <ben.knoble@gmail.com>,
Yoichi NAKAYAMA <yoichi.nakayama@gmail.com>,
Yoichi NAKAYAMA <yoichi.nakayama@gmail.com>
Subject: [PATCH v7 3/3] worktree add: improve message for ambiguous remote branch name
Date: Sat, 22 Aug 2026 03:22:42 +0000 [thread overview]
Message-ID: <095a5796d4c92012825daa07eef67140a7461018.1787368962.git.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.2197.v7.git.1787368962.gitgitgadget@gmail.com>
From: Yoichi NAKAYAMA <yoichi.nakayama@gmail.com>
When the user runs 'git worktree add ../foo-dir bar-topic' without
specifying a remote, and there is no local branch named bar-topic, we
try to guess which remote branch bar-topic refers to, then create a
new branch named bar-topic that tracks the remote branch.
If multiple remotes have a branch named bar-topic, we silently gave
up, leaving the variable 'branch' intact. We then entered the
conditional clause 'if (!opts.orphan &&
!lookup_commit_reference_by_name(branch))' and triggered an "invalid
reference" error. This error message did not provide enough
information to resolve the ambiguity.
When multiple matching branches are found, display a hint and a
descriptive error message and die immediately.
Signed-off-by: Yoichi NAKAYAMA <yoichi.nakayama@gmail.com>
---
builtin/worktree.c | 37 ++++++++++++++++++++++++++++++++++---
t/t2400-worktree-add.sh | 4 ++--
2 files changed, 36 insertions(+), 5 deletions(-)
diff --git a/builtin/worktree.c b/builtin/worktree.c
index 22c8e5e131..320b18873d 100644
--- a/builtin/worktree.c
+++ b/builtin/worktree.c
@@ -788,6 +788,25 @@ static char *dwim_branch(const char *path, char **new_branch)
return NULL;
}
+static void advise_disambiguating_remotes(const char *path, const char *branch,
+ const struct string_list *matched_remote_names)
+{
+ struct string_list_item *item;
+
+ advise(_("Branch name '%s' appears in multiple remotes:"), branch);
+ for_each_string_list_item(item, matched_remote_names) {
+ advise(_(" %s"), item->string);
+ }
+ advise(_("If you meant to create a worktree from a remote tracking branch on\n"
+ "<remote>, you can do so by:\n"
+ "\n"
+ " git worktree add -b %s %s <remote>/%s\n"
+ "\n"
+ "If you'd like to always prefer some remote, e.g. 'origin',\n"
+ "consider setting checkout.defaultRemote=origin in your config."),
+ branch, path, branch);
+}
+
static int add(int ac, const char **av, const char *prefix,
struct repository *repo UNUSED)
{
@@ -898,17 +917,29 @@ static int add(int ac, const char **av, const char *prefix,
/* DWIM: Infer --orphan when repo has no refs. */
opts.orphan = (!s) && dwim_orphan(&opts, !!opt_track, 1);
} else if (ac == 2) {
- struct object_id oid;
struct commit *commit;
- char *remote;
commit = lookup_commit_reference_by_name(branch);
if (!commit) {
- remote = unique_tracking_name(branch, &oid, NULL, NULL);
+ struct object_id oid;
+ char *remote;
+ int num_matches = 0;
+ struct string_list matched_remote_names = STRING_LIST_INIT_DUP;
+
+ remote = unique_tracking_name(branch, &oid, &num_matches,
+ &matched_remote_names);
if (remote) {
new_branch = branch;
branch = new_branch_to_free = remote;
+ } else if (num_matches > 1) {
+ if (!opts.quiet &&
+ advice_enabled(ADVICE_CHECKOUT_AMBIGUOUS_REMOTE_BRANCH_NAME))
+ advise_disambiguating_remotes(path, branch,
+ &matched_remote_names);
+ die(_("'%s' matched multiple (%d) remote tracking branches"),
+ branch, num_matches);
}
+ string_list_clear(&matched_remote_names, 0);
}
if (!strcmp(branch, "HEAD"))
diff --git a/t/t2400-worktree-add.sh b/t/t2400-worktree-add.sh
index 87b926728a..5c105cf252 100755
--- a/t/t2400-worktree-add.sh
+++ b/t/t2400-worktree-add.sh
@@ -624,12 +624,12 @@ test_expect_success '"add" <path> <branch> dwims' '
test_expect_success '"add" <path> <branch> dwims with checkout.defaultRemote' '
test_when_finished rm -rf repo_upstream repo_dwim foo &&
setup_remote_repo repo_upstream repo_dwim &&
- git init repo_dwim &&
(
cd repo_dwim &&
git remote add repo_upstream2 ../repo_upstream &&
git fetch repo_upstream2 &&
- test_must_fail git worktree add ../foo foo &&
+ test_must_fail git worktree add ../foo foo 2>error.actual &&
+ test_grep "matched multiple (2) remote tracking branches" error.actual &&
git -c checkout.defaultRemote=repo_upstream worktree add ../foo foo &&
git status -uno --porcelain >status.actual &&
test_must_be_empty status.actual
--
gitgitgadget
next prev parent reply other threads:[~2026-08-22 3:22 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 8:21 [PATCH] worktree add: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-08 17:00 ` Junio C Hamano
2026-08-08 21:57 ` Junio C Hamano
2026-08-09 7:45 ` Harald Nordgren
2026-08-09 18:19 ` Junio C Hamano
2026-08-10 10:12 ` Harald Nordgren
2026-08-09 18:17 ` Junio C Hamano
2026-08-10 13:04 ` Yoichi Nakayama
2026-08-10 13:00 ` Yoichi Nakayama
2026-08-10 13:07 ` D. Ben Knoble
2026-08-10 13:35 ` Yoichi Nakayama
2026-08-10 15:06 ` Junio C Hamano
2026-08-10 21:36 ` Yoichi Nakayama
2026-08-11 16:38 ` Ben Knoble
2026-08-12 13:14 ` Yoichi Nakayama
2026-08-10 15:07 ` [PATCH v2] " Yoichi NAKAYAMA via GitGitGadget
2026-08-10 20:55 ` [PATCH v3] " Yoichi NAKAYAMA via GitGitGadget
2026-08-11 0:03 ` Junio C Hamano
2026-08-11 6:31 ` Yoichi Nakayama
2026-08-12 19:22 ` Junio C Hamano
2026-08-15 4:36 ` Yoichi Nakayama
2026-08-11 6:35 ` [PATCH v4] " Yoichi NAKAYAMA via GitGitGadget
2026-08-19 12:50 ` [PATCH v5 0/2] " Yoichi NAKAYAMA via GitGitGadget
2026-08-19 12:50 ` [PATCH v5 1/2] checkout: " Yoichi NAKAYAMA via GitGitGadget
2026-08-19 22:54 ` D. Ben Knoble
2026-08-20 2:18 ` Junio C Hamano
2026-08-20 15:41 ` Yoichi Nakayama
2026-08-19 12:50 ` [PATCH v5 2/2] worktree add: " Yoichi NAKAYAMA via GitGitGadget
2026-08-20 21:03 ` [PATCH v6 0/3] " Yoichi NAKAYAMA via GitGitGadget
2026-08-20 21:03 ` [PATCH v6 1/3] checkout: extract function to display advice for ambiguous remotes Yoichi NAKAYAMA via GitGitGadget
2026-08-20 21:03 ` [PATCH v6 2/3] checkout: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-20 21:03 ` [PATCH v6 3/3] worktree add: " Yoichi NAKAYAMA via GitGitGadget
2026-08-21 3:54 ` Junio C Hamano
2026-08-21 23:15 ` Yoichi Nakayama
2026-08-21 23:49 ` Junio C Hamano
2026-08-22 0:50 ` Yoichi Nakayama
2026-08-22 17:22 ` Junio C Hamano
2026-08-24 22:25 ` Yoichi Nakayama
2026-08-22 3:22 ` [PATCH v7 0/3] " Yoichi NAKAYAMA via GitGitGadget
2026-08-22 3:22 ` [PATCH v7 1/3] checkout: extract function to display advice for ambiguous remotes Yoichi NAKAYAMA via GitGitGadget
2026-08-22 3:22 ` [PATCH v7 2/3] checkout: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-22 3:22 ` Yoichi NAKAYAMA via GitGitGadget [this message]
2026-08-22 18:08 ` [PATCH v7 0/3] worktree add: " Junio C Hamano
2026-08-25 21:04 ` [PATCH v8 0/4] " Yoichi NAKAYAMA via GitGitGadget
2026-08-25 21:04 ` [PATCH v8 1/4] checkout: extract function to display advice for ambiguous remotes Yoichi NAKAYAMA via GitGitGadget
2026-08-25 21:04 ` [PATCH v8 2/4] checkout: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-25 21:04 ` [PATCH v8 3/4] worktree add: " Yoichi NAKAYAMA via GitGitGadget
2026-08-25 21:04 ` [PATCH v8 4/4] worktree add: treat multiple matches with --guess-remote as an error Yoichi NAKAYAMA via GitGitGadget
2026-08-25 21:31 ` Junio C Hamano
2026-08-26 10:45 ` [PATCH v9 0/4] worktree add: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-26 10:45 ` [PATCH v9 1/4] checkout: extract function to display advice for ambiguous remotes Yoichi NAKAYAMA via GitGitGadget
2026-08-26 15:24 ` Junio C Hamano
2026-08-26 10:45 ` [PATCH v9 2/4] checkout: improve message for ambiguous remote branch name Yoichi NAKAYAMA via GitGitGadget
2026-08-26 16:46 ` Junio C Hamano
2026-08-26 10:45 ` [PATCH v9 3/4] worktree add: " Yoichi NAKAYAMA via GitGitGadget
2026-08-26 10:45 ` [PATCH v9 4/4] worktree add: treat multiple matches with --guess-remote as an error Yoichi NAKAYAMA via GitGitGadget
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=095a5796d4c92012825daa07eef67140a7461018.1787368962.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=haraldnordgren@gmail.com \
--cc=yoichi.nakayama@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.