Open joecarl opened 2 months ago
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
Hi,
I’m currently working on a remote Linux server via SSH using VSCode, and I’ve noticed a significant difference in the way VSCode handles cloning repositories from GitHub compared to Azure DevOps.
For GitHub repositories, VSCode handles the OAuth credential management seamlessly. When I clone a GitHub repository, it only asks for my credentials the first time, and I believe it’s VSCode managing this process, making it extremely convenient.
However, when I try to clone a repository from Azure DevOps, this seamless integration is missing. I have to resort to using tools like Git Credential Manager, configuring GPG keys, or setting up other complex solutions. While I have been able to get these methods working, they are cumbersome and add unnecessary complexity to the workflow.
I also tried the Azure Repos extension, but it’s not a good solution. It seems to clone the repository in an isolated environment where I can only edit code — no access to the console, no debugging capabilities, nothing beyond basic code editing. This severely limits its usefulness for any real development work.
Is there any way that VSCode can handle cloning Azure DevOps repositories in a similar way to GitHub? It would be fantastic if the OAuth process for Azure DevOps could be integrated into VSCode just like it is for GitHub, allowing for a smoother experience.
Thanks for considering this feature request!