On 2023-12-27 at 17:11:31, Brian Hart wrote:
> Hello,
Hey,
> 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
> ```
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.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
Attachment:
signature.asc
Description: PGP signature
