git-ecosystem / git-ecosystem/git-credential-manager
Interactive credential flow does not trigger on fetch
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
Windows 11 pro, x64
Git hosting provider(s)
Azure DevOps
Other hosting provider
No response
(Azure DevOps only) What format is your remote URL?
https://{org}.visualstudio.com
Can you access the remote repository directly in the browser?
Yes, I can access the repository
Expected behavior
The credential manager flow triggers when accessing the remote.
C:\src\foo>git fetch origin master
remote: Azure Repos
remote: Found 26 objects to send. (1365 ms)
Actual behavior
The credential manager flow does not trigger on fetch, but triggers on pull:
C:\src\foo>git fetch origin master
fatal: Authentication failed for 'https://foo.visualstudio.com/DefaultCollection/Bar/_git/Baz/'
C:\src\foo>git pull
remote: Azure Repos
remote: Found 26 objects to send. (1365 ms)
Unpacking objects: 100% (26/26), 13.46 KiB | 115.00 KiB/s, done.
From https://foo.visualstudio.com/DefaultCollection/Bar/_git/Baz/
- branch foo/bar -> FETCH_HEAD
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
Reproduce the Windows 11 failure using the reported Azure DevOps remote URL, comparing git fetch origin master with git pull. Trace the credential manager flow involved in each command; done means fetch triggers the credential flow and successfully retrieves the remote data instead of returning an authentication failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100