From: Junio C Hamano <gitster@pobox.com>
To: Yoichi Nakayama <yoichi.nakayama@gmail.com>
Cc: Yoichi NAKAYAMA via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, Harald Nordgren <haraldnordgren@gmail.com>,
"D. Ben Knoble" <ben.knoble@gmail.com>
Subject: Re: [PATCH v3] worktree add: improve message for ambiguous remote branch name
Date: Wed, 12 Aug 2026 12:22:55 -0700 [thread overview]
Message-ID: <xmqqjypvw3cg.fsf@gitster.g> (raw)
In-Reply-To: <CAF5D8-uCjA-MFtdBCa0+5PDb-LFJ7JJ0yK1AtuWCKEN+tKQa_Q@mail.gmail.com> (Yoichi Nakayama's message of "Tue, 11 Aug 2026 15:31:54 +0900")
Yoichi Nakayama <yoichi.nakayama@gmail.com> writes:
>> Instead of throwing the problem back to the user with four extra
>> lines of message telling them how to run 'git branch', I would have
>> expected this patch to teach unique_tracking_name() to optionally
>> return the list of remotes with that branch name, and to use that
>> result in this message. However, if the goal is simply to provide
>> something better than 'invalid reference', we do not even need to
>> go that far. Just stating that branch 'y' appears on multiple
>> remotes and asking them to clarify which one they mean might be a
>> sufficient improvement.
>
> Extending `unique_tracking_name()` would also affect the implementation
> in `checkout.c`, and since the goal here is to improve the messages
> (making them as helpful as those in `checkout`), I will hold off on doing
> that for now.
Sorry but I do not quite understand this logic.
Giving unique_tracking_name() the optional ability to report which
remotes have a branch with the given name does not have to affect
other callers of the function at all; that is the definition of a
new feature being "optional."
Furthermore, the goal of improving these messages falls short if we
withhold the list of remotes the user could have meant, which we are
already computing internally to decide that the original request is
ambiguous.
>> Could the original request be aiming to create a new worktree with
>> the HEAD detached at the commit pointed at by the remote-tracking
>> branch, instead of creating a local branch forked from it? I am
>> just wondering if "-b %s" is too specific to one possible
>> interpretation that may contradict to what the user actually wanted
>> to do.
>
> If the user is aiming to create a new worktree with the HEAD detached,
> one would specify a fully qualified branch name like origin/bar-topic,
> starting with a remote name.
I am not sure about this part, either. After all, we are trying to
help a user who made a mistake composing their command-line
arguments. If they specify a fully qualified branch name like
'origin/bar-topic' (regardless of whether they want to create a
detached 'HEAD' or not), they would not hit the 'saying bar-topic
alone is ambiguous' error path, would they?
Here is a patch to show what I mean. To 'improve the message for an
ambiguous remote branch name' for the 'checkout' command, we can add
this optional feature to the unique_tracking_name() function and we
can do so without affecting the 'worktree add' command.
Regardless of whether we modify unique_tracking_name(), I think
refactoring be_explicit() is worth doing, as the original code in
parse_remote_branch() was badly misindented.
builtin/checkout.c | 74 ++++++++++++++++++++++++++++++++----------------------
builtin/worktree.c | 4 +--
checkout.c | 14 +++++++++--
checkout.h | 5 +++-
4 files changed, 62 insertions(+), 35 deletions(-)
diff --git c/builtin/checkout.c w/builtin/checkout.c
index 55e3a89a85..8d61973a11 100644
--- c/builtin/checkout.c
+++ w/builtin/checkout.c
@@ -1343,13 +1343,50 @@ enum checkout_command {
CHECKOUT_RESTORE = 3,
};
+static void be_explicit(enum checkout_command which_command,
+ const struct string_list *matched_remote_names)
+{
+ const char *cmdname;
+ struct string_list_item *item;
+
+ switch (which_command) {
+ case CHECKOUT_CHECKOUT:
+ cmdname = "checkout";
+ break;
+ case CHECKOUT_SWITCH:
+ cmdname = "switch";
+ break;
+ default:
+ BUG("command <%d> should not reach parse_remote_branch",
+ which_command);
+ break;
+ }
+
+ advise(_("Branches with the same name appears in multiple remotes:"));
+ for_each_string_list_item(item, matched_remote_names) {
+ advise(_(" %s"), item->string);
+ }
+ advise(_("If you meant to check out a remote tracking branch on, e.g. 'origin',\n"
+ "you can do so by fully qualifying the name with the --track option:\n"
+ "\n"
+ " git %s --track origin/<name>\n"
+ "\n"
+ "If you'd like to always have checkouts of an ambiguous <name> prefer\n"
+ "one remote, e.g. the 'origin' remote, consider setting\n"
+ "checkout.defaultRemote=origin in your config."),
+ cmdname);
+}
+
static char *parse_remote_branch(const char *arg,
struct object_id *rev,
int could_be_checkout_paths,
enum checkout_command which_command)
{
int num_matches = 0;
- char *remote = unique_tracking_name(arg, rev, &num_matches);
+ struct string_list matched_remote_names = STRING_LIST_INIT_DUP;
+
+ char *remote = unique_tracking_name(arg, rev, &num_matches,
+ &matched_remote_names);
if (remote && could_be_checkout_paths) {
die(_("'%s' could be both a local file and a tracking branch.\n"
@@ -1358,37 +1395,14 @@ static char *parse_remote_branch(const char *arg,
}
if (!remote && num_matches > 1) {
- if (advice_enabled(ADVICE_CHECKOUT_AMBIGUOUS_REMOTE_BRANCH_NAME)) {
- const char *cmdname;
-
- switch (which_command) {
- case CHECKOUT_CHECKOUT:
- cmdname = "checkout";
- break;
- case CHECKOUT_SWITCH:
- cmdname = "switch";
- break;
- default:
- BUG("command <%d> should not reach parse_remote_branch",
- which_command);
- break;
- }
-
- advise(_("If you meant to check out a remote tracking branch on, e.g. 'origin',\n"
- "you can do so by fully qualifying the name with the --track option:\n"
- "\n"
- " git %s --track origin/<name>\n"
- "\n"
- "If you'd like to always have checkouts of an ambiguous <name> prefer\n"
- "one remote, e.g. the 'origin' remote, consider setting\n"
- "checkout.defaultRemote=origin in your config."),
- cmdname);
- }
-
- die(_("'%s' matched multiple (%d) remote tracking branches"),
- arg, num_matches);
+ if (advice_enabled(ADVICE_CHECKOUT_AMBIGUOUS_REMOTE_BRANCH_NAME))
+ be_explicit(which_command, &matched_remote_names);
+ die(_("'%s' matched multiple (%d) remote tracking branches"),
+ arg, num_matches);
}
+ string_list_clear(&matched_remote_names, 0);
+
return remote;
}
diff --git c/builtin/worktree.c w/builtin/worktree.c
index 654d27c3e1..22c8e5e131 100644
--- c/builtin/worktree.c
+++ w/builtin/worktree.c
@@ -782,7 +782,7 @@ static char *dwim_branch(const char *path, char **new_branch)
*new_branch = branchname;
if (guess_remote) {
struct object_id oid;
- char *remote = unique_tracking_name(*new_branch, &oid, NULL);
+ char *remote = unique_tracking_name(*new_branch, &oid, NULL, NULL);
return remote;
}
return NULL;
@@ -904,7 +904,7 @@ static int add(int ac, const char **av, const char *prefix,
commit = lookup_commit_reference_by_name(branch);
if (!commit) {
- remote = unique_tracking_name(branch, &oid, NULL);
+ remote = unique_tracking_name(branch, &oid, NULL, NULL);
if (remote) {
new_branch = branch;
branch = new_branch_to_free = remote;
diff --git c/checkout.c w/checkout.c
index 1588b116ee..2806b783ec 100644
--- c/checkout.c
+++ w/checkout.c
@@ -8,6 +8,7 @@
#include "checkout.h"
#include "config.h"
#include "strbuf.h"
+#include "string-list.h"
struct tracking_name_data {
/* const */ char *src_ref;
@@ -17,6 +18,7 @@ struct tracking_name_data {
const char *default_remote;
char *default_dst_ref;
struct object_id *default_dst_oid;
+ struct string_list **remote_names;
};
#define TRACKING_NAME_DATA_INIT { 0 }
@@ -39,6 +41,8 @@ static int check_tracking_name(struct remote *remote, void *cb_data)
oidcpy(dst, cb->dst_oid);
cb->default_dst_oid = dst;
}
+ if (cb->remote_names)
+ string_list_append(*cb->remote_names, remote->name);
if (cb->dst_ref) {
free(query.dst);
return 0;
@@ -48,14 +52,20 @@ static int check_tracking_name(struct remote *remote, void *cb_data)
}
char *unique_tracking_name(const char *name, struct object_id *oid,
- int *dwim_remotes_matched)
+ int *dwim_remotes_matched,
+ struct string_list *dwim_remote_names)
{
struct tracking_name_data cb_data = TRACKING_NAME_DATA_INIT;
const char *default_remote = NULL;
- if (!repo_config_get_string_tmp(the_repository, "checkout.defaultremote", &default_remote))
+
+ if (!repo_config_get_string_tmp(the_repository,
+ "checkout.defaultremote",
+ &default_remote))
cb_data.default_remote = default_remote;
cb_data.src_ref = xstrfmt("refs/heads/%s", name);
cb_data.dst_oid = oid;
+ if (dwim_remote_names)
+ cb_data.remote_names = &dwim_remote_names;
for_each_remote(check_tracking_name, &cb_data);
if (dwim_remotes_matched)
*dwim_remotes_matched = cb_data.num_matches;
diff --git c/checkout.h w/checkout.h
index 55920e7aeb..0b185a0fc9 100644
--- c/checkout.h
+++ w/checkout.h
@@ -3,6 +3,8 @@
#include "hash.h"
+struct string_list;
+
/*
* Check if the branch name uniquely matches a branch name on a remote
* tracking branch. Return the name of the remote if such a branch
@@ -10,6 +12,7 @@
*/
char *unique_tracking_name(const char *name,
struct object_id *oid,
- int *dwim_remotes_matched);
+ int *dwim_remotes_matched,
+ struct string_list *dwim_remote_names);
#endif /* CHECKOUT_H */
next prev parent reply other threads:[~2026-08-12 19:22 UTC|newest]
Thread overview: 21+ 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 [this message]
2026-08-11 6:35 ` [PATCH v4] " 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=xmqqjypvw3cg.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox