Extension stuck on configuring remotes with global "url aliasing"

[tulis-deshaw]

• Extension version: 0.144.0
• VSCode Version: Version: 1.120.0
• OS: Windows_NT x64 10.0.22631
• Repository Clone Configuration (single repository/fork of an upstream repository): single repository
• GitHub Product (GitHub.com/GitHub Enterprise version x.x.x): GitHub Enterprise Version 3.18.8

Steps to Reproduce:

Some information about out config. We have our own GitHub Enterprise Version and we allow users to clone a repo using git clone github:<org>/<repo>. We have the following added to our global git config url.https://github.abc.com/.insteadof=github: which makes this works. Whenever we open a repo, the extension does not read this config and tries to resolve using https://github.com instead of https://github.abc.com.

1. Add url.https://github.abc.com/.insteadof=github: to the global git config
2. Clone a repo using git clone github:<org>/<repo>. Check that when you run git config --get remote.origin.url, it should return github:/
3. Now if you see the Extension Output then it tried to resolve using https://github.com/org/repo instead of https://github.sbc.com/org/repo.

This gets resolved locally when we run git remote set-url origin https://github.abc.com/org/repo. Can you please check this out and fix it?

[alexr00]

Upstream issue with VS Code: microsoft/vscode#174941