Auto-detection of git remote doesn't work for project containing spaces

[rorueda]

• Extension version: 1.0.0

Steps to Reproduce:

1. Open a workspace where the remote is configured with a url in which the project contains spaces and it is percent-encoded (e.g. git@ssh.dev.azure.com:v3/myorg/my%20project/myrepo). Note that this is how AzDO presents the url in the clone option.
2. Try to sign in

Workaround:

Configure the remote url with an actual space instead of the percent-encoded space.

[Simonmaignan]

@rorueda , can you please clarify your workaround? Where do you change the remote url?
I tried to change my remote url in .git/config, but I then get the following git error

fatal: unable to access 'https://dev.azure.com/my-account/My Project/_git/my-git-repo/': URL rejected: Malformed input to a URL function

[Simonmaignan]

On my side, I don't understand the Azdo VS Code extension error message

[Info] AzdoRepository> Inferring org config from url: https://dev.azure.com/my-account/My Project/_git/my-git-repo/
[Info] AzdoRepository> Inferred orgUrl: https://dev.azure.com/my-account, projectName: My%20Project
[Info] AzdoRepository> Selected orgUrl: https://dev.azure.com/my-account, projectName: My%20Project
[Info] Review> Validate state in progress
[Info] Review> Validating state...
[Info] FolderRepositoryManager> No remote with name 'upstream' found. All other remotes: origin
[Info] FolderRepositoryManager> Found Azdo remotes origin
[Info] Review> Queuing additional validate state
[Info] Review> Queuing additional validate state
[Info] Review> no matching pull request metadata found for current branch main
[Info] AzdoRepository> Fetching pull requests for search: {"sourceRefName":"main"} failed: AggregateError
[Info] AzdoRepository> Fetching pull requests for search: {"reviewerId":"16f8b2ce-d0d1-64a6-9c45-d29306aaf846","status":1} failed: Error: A project name is required in order to reference a Git repository by name.

It seems that the extension is able to retrieve the project name from the git remote url, but somehow, it still complains that a project name is needed.

[Simonmaignan]

Forget my previous comments, I was able to fix the issue by reading the comments from #61