From: Ernesto Alfonso <erjoalgo@gmail.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: disable interactive prompting
Date: Wed, 04 Oct 2017 10:46:04 -0700 [thread overview]
Message-ID: <878tgqhkmb.fsf@gmail.com> (raw)
In-Reply-To: <20171004170532.6pjcwdurcokpvcop@sigill.intra.peff.net> (Jeff King's message of "Wed, 4 Oct 2017 13:05:32 -0400")
Thanks for pointing out the option.
I tried "git help push" and searched for "prompt", "interactive",
"credentials"...
I don't think I would have figured to try
"git help git" from "git help" even after reading it carefully.
I'd suggest adding a hint in "git help".
I also don't seem have the GIT_TERMINAL_PROMPT in "git version 1.8.3.1" but I can fix this.
Thanks,
Ernesto
Jeff King <peff@peff.net> writes:
> On Wed, Oct 04, 2017 at 09:10:48AM -0700, Ernesto Alfonso wrote:
>
>> Waiting for git-push synchronously slows me down, so I have a bash
>> alias/function to do this in the background. But when my origin is https, I
>> get an undesired interactive prompt. I've tried to disable by
>> redirecting stdin:
>>
>> git push ${REMOTE} ${BRANCH} &>/dev/null </dev/null
>>
>> but I still get an interactive prompt.
>>
>> Is there a way to either
>>
>> 1. disable interactive prompting
>> 2. programmatically determine whether a git command (or at least a git
>> push) would interactively prompt
>
> I assume the prompt is for credentials, since that's generally the only
> thing git-push will prompt for.
>
> Try:
>
> $ git help git | sed -ne '/PROMPT/,/^$/p'
> GIT_TERMINAL_PROMPT
> If this environment variable is set to 0, git will not prompt on
> the terminal (e.g., when asking for HTTP authentication).
>
> Of course that just stops the prompting. If Git needs a credential and
> you don't provide it, then the push will fail.
>
> For advice on that that, try "git help credentials".
>
> -Peff
prev parent reply other threads:[~2017-10-04 17:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 16:10 disable interactive prompting Ernesto Alfonso
2017-10-04 17:01 ` Jonathan Nieder
2017-10-04 17:09 ` Ernesto Alfonso
2017-10-04 17:05 ` Jeff King
2017-10-04 17:46 ` Ernesto Alfonso [this message]
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=878tgqhkmb.fsf@gmail.com \
--to=erjoalgo@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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).