git-ecosystem / git-ecosystem/git-credential-manager
Credential-Manager only works for github if the User name in Windows Credential is everything but the actual github user name
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
Version
2.5.0+d34930736e131ad80e5690e5634ced1808aff3e2
Operating system
Windows
OS version or distribution
10 Pro 19045.4412
Git hosting provider(s)
GitHub
Other hosting provider
No response
(Azure DevOps only) What format is your remote URL?
None
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
After installing git for windows on the machine I did a first git clone . This asked me for Authentication via git-credential-manager and stored the credentials in the Windows Credentials.
The next time I did a git fetch (or any other git command that requires authentication) I expected the stored credentials to be used. Especially I expect my actual git User Name to be required.
Actual behavior
I get a git-credential-manager popup every time I interact with github via a git command that requires to be authenticated
Then I found https://github.com/git-ecosystem/git-credential-manager/issues/1555#issuecomment-2148567509
And indeed, changing the User Name in Windows Credentials to "1" lets me run i.e. git pull without getting the git-credential-manager popup
Actually, it seems I can set the User Name to anything as long as it is not my real github username.
Logs
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start by reproducing the GitHub authentication flow on Windows 10 with Git Credential Manager 2.5.0, then inspect how Windows Credential Manager handles the stored username. Done means authenticated GitHub commands reuse the credential without a popup while the actual GitHub username remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, github
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100