You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Like the title says, if you clone a git repo from VSTS with the old ssh://acctname@acctname.visualstudio.com:22/DefaultCollection/_git/reponame URL, the vscode vsts extension will correctly detect it as a vsts repo. If, on the other hand, you update the remote to the new ssh://acctname@vs-ssh.visualstudio.com:22/DefaultCollection/_ssh/reponame format, the extension won't recognize it as a vsts workspace.
I checked for updates to the extension -- there don't appear to be any. For the time being I've just switched back to the old URL scheme, but as the giant deprecation banner warns when pulling from it, it's going away on the 17th.
It looks like the parsing code begins here and eventually winds up here. Since the VSTS clone URLs now use _ssh for that segment of the path, this won't cut it anymore.
The text was updated successfully, but these errors were encountered:
I skimmed the open issues and PRs, doesn't look like this has been addressed yet, so I'll cut a PR quickly to remove the nesting (since clearly a git repo cloned from visualstudio.com is a VSTS repo)
Unfortunately, the ssh URLs have changed again to something like: acctname@vs-ssh.visualstudio.com:v3/acctname/DefaultCollection/reponame which breaks the detection (again).
Like the title says, if you clone a git repo from VSTS with the old
ssh://acctname@acctname.visualstudio.com:22/DefaultCollection/_git/reponame
URL, the vscode vsts extension will correctly detect it as a vsts repo. If, on the other hand, you update the remote to the newssh://acctname@vs-ssh.visualstudio.com:22/DefaultCollection/_ssh/reponame
format, the extension won't recognize it as a vsts workspace.I checked for updates to the extension -- there don't appear to be any. For the time being I've just switched back to the old URL scheme, but as the giant deprecation banner warns when pulling from it, it's going away on the 17th.
It looks like the parsing code begins here and eventually winds up here. Since the VSTS clone URLs now use _ssh for that segment of the path, this won't cut it anymore.
The text was updated successfully, but these errors were encountered: