Suppress 'info: please complete authentication in browser'

Git for Windows version: 2.43.0

Hello,

I am running a nightly shell script that syncs my local and remote Git repos. It kicks off at 7:30 PM each day. When I come into work the following morning, sporadically, I find that part of the script has not been executing for hours because a modal popup displays.

The text in the console is: `info: please complete authentication in your browser`

At the same time, a modal pop-up appears. The modal popup needs a button clicked to open the browser and sign in. Upon doing so, the browser says "authentication successful," and the script continues -- but this is after I've woken up from being asleep, with the script otherwise sitting suspended all night long.

I've heard various suggestions before about using the Windows Credential Manager (I believe I am already) and such. It seems as if Git is programmed to ignore the Credential Manager periodically and demand the use of the browser to re-authenticate.

Here is the .sh script I am using, e.g., to do a pull on each directory in a root directory:

``` git config --global user.email "XXXXX" --replace-all; git config --global user.name "XXXXXX" --replace-all; git config --global credential.helper wincred --replace-all; for d in */; do cd $d; echo Processing repository in "${d%/}"...; git config credential.helper wincred; git remote update; git pull --all -v --no-rebase; git add --renormalize .; cd ..; done ```

As you can see I am using `git config --global credential.helper wincred --replace-all` and I am not sure why this should not work. NOTE: The 'XXXX' are for privacy.

How can I suppress the modal pop-up so I can run my overnight Git scripts?

Regards,

Brian Hart

On 2023-12-27 at 17:11:31, Brian Hart wrote:

Hey,

If your goal is to use a specific configuration, you may find it easier to use the GIT_CONFIG_GLOBAL environment variable to set a custom global configuration file and then GIT_CONFIG_NOSYSTEM=1 to unset the system configuration from being used. My guess is that there's a `credential.helper=manager` setting in some config file, which you'd be able to see with `git config -l --show-origin`, and that using this configuration would fix that.

However, if you see this problem after that, I'd recommend contacting the Git for Windows team on their issue tracker at https://github.com/git-for-windows/git/issues/ or the Git Credential Manager Core team at https://github.com/git-ecosystem/git-credential-manager/issues/. The Git project itself doesn't distribute any binaries or anything but the core Git code itself, so if you have a problem with Git for Windows or Git Credential Manager Core, you should contact those folks directly.