path: root/builtin/push.c
diff options
authorJunio C Hamano <>2016-10-28 19:25:30 (GMT)
committerJunio C Hamano <>2016-10-29 06:30:30 (GMT)
commiteef2bdaa4a979994a22dbc5c2e7c5b8a9d2a2043 (patch)
treead1046accea45420eb173cc2d80c954bc5b918e2 /builtin/push.c
parent0b65a8dbdb38962e700ee16776a3042beb489060 (diff)
push: do not use potentially ambiguous default refspec
When the user does the lazy "git push" with no parameters with push.default set to either "upstream", "simple" or "current", we internally generated a refspec that has the current branch name on the source side and used it to push. However, the branch name (say "test") may be an ambiguous refname in the context of the source repository---there may be a tag with the same name, for example. This would trigger an unnecessary error without any fault on the end-user's side. Be explicit and give a full refname as the source side to avoid the ambiguity. The destination side when pushing with the "current" sent only the name of the branch and forcing the receiving end to guess, which is the same issue. Be explicit there as well. Reported-by: Kannan Goundan <> Signed-off-by: Junio C Hamano <>
Diffstat (limited to 'builtin/push.c')
1 files changed, 5 insertions, 2 deletions
diff --git a/builtin/push.c b/builtin/push.c
index 4e9e4db..00a1b68 100644
--- a/builtin/push.c
+++ b/builtin/push.c
@@ -194,15 +194,18 @@ static void setup_push_upstream(struct remote *remote, struct branch *branch,
die_push_simple(branch, remote);
- strbuf_addf(&refspec, "%s:%s", branch->name, branch->merge[0]->src);
+ strbuf_addf(&refspec, "%s:%s", branch->refname, branch->merge[0]->src);
static void setup_push_current(struct remote *remote, struct branch *branch)
+ struct strbuf refspec = STRBUF_INIT;
if (!branch)
die(_(message_detached_head_die), remote->name);
- add_refspec(branch->name);
+ strbuf_addf(&refspec, "%s:%s", branch->refname, branch->refname);
+ add_refspec(refspec.buf);
static int is_workflow_triangular(struct remote *remote)