Problem
Azure DevOps repositories using the standard SSH remote format (git@ssh.dev.azure.com:v3/...) are classified as an unknown source-control provider. T3 Code can detect the Azure CLI, but active Azure DevOps pull requests are not shown.
Reproduction
- Open a repository whose remote uses
git@ssh.dev.azure.com:v3/....
- Check out a branch with an active Azure DevOps pull request.
- Observe that the pull request is not detected in the current checkout or project status.
Expected behavior
The repository should be classified as Azure DevOps and its active pull request should be detected through the Azure CLI.
Verification
This was reproduced with a real Azure DevOps-backed repository in a local T3 development environment. After adding SSH-host detection, the existing active pull request appeared in the UI.
Problem
Azure DevOps repositories using the standard SSH remote format (
git@ssh.dev.azure.com:v3/...) are classified as an unknown source-control provider. T3 Code can detect the Azure CLI, but active Azure DevOps pull requests are not shown.Reproduction
git@ssh.dev.azure.com:v3/....Expected behavior
The repository should be classified as Azure DevOps and its active pull request should be detected through the Azure CLI.
Verification
This was reproduced with a real Azure DevOps-backed repository in a local T3 development environment. After adding SSH-host detection, the existing active pull request appeared in the UI.