From: Pierre Demailly <pierredemailly.pro@gmail.com>
To: git@vger.kernel.org
Subject: [feature request] keep flags when trying to push with no upstream branch
Date: Wed, 22 Apr 2020 16:18:14 +0200 [thread overview]
Message-ID: <CAMmcmXZPxNYmVMzLydKpAzYN=qRhNRr048EA9mairZ9t_22j-w@mail.gmail.com> (raw)
Hello,
Didn't find how to submit a feature request on github, hope i'm at the
right place.
When using command git push, if the current branch hasn't upstream
branch, an error is submitted with following message:
> 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 origin current_branch
It would be well to give the command to use with previous used flags.
Example: git push --no-verify
>
> 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 origin current_branch --no-verify
I didn't find any place to see features request list, so I don't know
if someone already asked for this feature, I'm sorry if it's the case.
Regards.
Pierre.
reply other threads:[~2020-04-22 14:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMmcmXZPxNYmVMzLydKpAzYN=qRhNRr048EA9mairZ9t_22j-w@mail.gmail.com' \
--to=pierredemailly.pro@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.
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 NNTP newsgroup(s).