From: Mathias Kunter <mathiaskunter@gmail.com>
To: git@vger.kernel.org
Subject: git push doesn't use local branch name as default
Date: Thu, 27 May 2021 19:06:25 +0200 [thread overview]
Message-ID: <065528bf-b496-83d3-767d-2a78e50a9edf@gmail.com> (raw)
Hi all,
at https://git-scm.com/docs/git-push#_description it says:
> When neither the command-line nor the configuration specify what to
> push, the default behavior is used, which corresponds to the simple
> value for push.default: the current branch is pushed to the
> corresponding upstream branch, but as a safety measure, the push is
> aborted if the upstream branch does not have the same name as the local
> one.
However, on a branch which does *not* have an upstream branch
configured, the command
> git push <remote_name>
doesn't use the local branch name as default, but fails with an error
instead:
> fatal: The current branch master has no upstream branch.
> To push the current branch and set the remote as upstream, use
>
> git push --set-upstream <remote_name> master
Note that it *does* work if the remote branch name is explicitly specified:
> git push <remote_name> <branch_name>
But shouldn't this also work without having to explicitly specify the
remote branch name, and default to the local branch name instead?
[System Info]
git version:
git version 2.31.1.windows.1
cpu: x86_64
built from commit: c5f0be26a7e3846e3b6268d1c6c4800d838c6bbb
sizeof-long: 4
sizeof-size_t: 8
shell-path: /bin/sh
feature: fsmonitor--daemon
uname: Windows 10.0 19042
compiler info: gnuc: 10.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>
[Enabled Hooks]
next reply other threads:[~2021-05-27 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 17:06 Mathias Kunter [this message]
2021-05-27 19:51 ` git push doesn't use local branch name as default Felipe Contreras
[not found] <3b9bc214-a30a-ba49-af96-7eeaf37b7bbd@gmail.com>
2021-05-28 6:29 ` Mathias Kunter
2021-05-28 7:00 ` Elijah Newren
2021-05-28 7:44 ` Mathias Kunter
2021-05-28 8:51 ` Mathias Kunter
2021-05-28 17:52 ` Felipe Contreras
2021-05-28 17:22 ` Felipe Contreras
2021-05-28 17:44 ` Elijah Newren
2021-05-28 18:58 ` Felipe Contreras
2021-05-28 17:10 ` Felipe Contreras
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=065528bf-b496-83d3-767d-2a78e50a9edf@gmail.com \
--to=mathiaskunter@gmail.com \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).