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
This is just to capture an issue for people searching for the same issue.
The schema validation was not working for a repository that is hosted on Azure DevOps Service. The issue resulted in being the URI of the origin. This particular repository had originally been cloned using the older visualstudio.com URI schema (this did not validate)
e.g. https://<Organisation>.visualstudio.com/<Project>/_git/<Repo>
Creating a new repo clone using the newer URI schema (this did validate)
e.g. https://<PAT>@dev.azure.com/<Organisation>/<Project>/_git/<Repo>
The text was updated successfully, but these errors were encountered:
Interesting, thanks for reporting @drewkg. Can you describe what you mean when you say "schema validation"? Do you mean the new schema auto-detection feature, or something else?
Apologies, I mean the ability to detect and download the json schema for your instance of Azure DevOps Service which includes the custom plugins that you have installed.
I have only just discovered this VS Code extension so I am unsure if this is new, but it is very useful.
This is just to capture an issue for people searching for the same issue.
The schema validation was not working for a repository that is hosted on Azure DevOps Service. The issue resulted in being the URI of the origin. This particular repository had originally been cloned using the older visualstudio.com URI schema (this did not validate)
e.g.
https://<Organisation>.visualstudio.com/<Project>/_git/<Repo>
Creating a new repo clone using the newer URI schema (this did validate)
e.g.
https://<PAT>@dev.azure.com/<Organisation>/<Project>/_git/<Repo>
The text was updated successfully, but these errors were encountered: