We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.5.0+d34930736e131ad80e5690e5634ced1808aff3e2
Windows
Windows 11 pro, x64
Azure DevOps
No response
https://{org}.visualstudio.com
Yes, I can access the repository
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)
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
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/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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.
Actual behavior
The credential manager flow does not trigger on fetch, but triggers on pull:
Logs
No response
The text was updated successfully, but these errors were encountered: