Constant reprompt for HTTPS authentication credentials via Gittyup after installation of `git-credential-manager`

[beedell-roke]

1. Version

   2.0.935+8b4735fc7b (from 8b4735f, per https://github.com/search?q=repo%3Agit-ecosystem%2Fgit-credential-manager+8b4735fc7b&type=commits).

2. Operating system

   < cpe:/o:opensuse:tumbleweed:20240304

3. Git hosting provider(s)

   https://gitlab.com/rokejulianlockhart/rokejulianlockhart/-/tree/5cc97ce1825e40c9ef8cb7f5044d1409d2089a1a

4. Can you access the remote repository directly in the browser?

   Yes, I can access the repository.

5. Expected behaviour

   I shouldn't be prompted more than once, surely?

6. Actual behaviour

   I'm prompted for every action.

7. Logs

   1. WSLENV=$WSLENV:GCM_TRACE:GIT_TRACE GCM_TRACE=1 GIT_TRACE=1 git fetch

      outputs

   2. WSLENV=$WSLENV:GCM_TRACE:GIT_TRACE: The term 'WSLENV=$WSLENV:GCM_TRACE:GIT_TRACE' is not recognized as a name of a cmdlet, function, script file, or executable program.
      Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
      

[beedell-roke]

#1210 (comment)

@RokeJulianLockhart, uninstallation per https://github.com/git-ecosystem/git-credential-manager/blob/7794843557439c1ce3c968a9b57a4f470b366bd1/docs/install.md#uninstall-5 remediates the problem.

[Joekie030]

.?

[beedell-roke]

#1210 (comment)

@Joekie030, I don't know what #1210 (comment) means.

[ldennington]

@rokejulianlockhart - since uninstallation worked can we close this issue? Or is further action needed?

[beedell-roke]

#1210 (comment)

@ldennington, of course, more work is needed. How is this project, which purports to be the eventual successor to the current fragmented authentication system, not requiring improvement if the sole fix is to uninstall it…?

[ldennington]

I misunderstood - I thought you meant it worked after uninstalling and re-installing. I will leave the issue open.

[ldennington]

Closing stale issue. If this is still a problem, please ensure you have installed the latest version. If the issue persists after that, please open a new issue ensuring you include the logs requested in the issue template.