Unable to parse remote 'ssh://**'. Please check that it is correctly formatted.
Hi @SanJin-hx, if your remote is literally ssh://****, the extension is showing this warning because it isn't about to extract the authority, owner, and repository name from it. You can change the remote with git remote set-url <remote name> <remote url> or you can remove it with git remote remove.
If your remote is not literally ssh://***, could you include more details about what it actually is, replacing whatever parts of it are data you don't want to share?
@RMacfarlane I'm getting a similar kind of error with SSH remotes, any thoughts?

09:33 $ git remote -v
heroku [email protected]:#####.git (fetch)
heroku [email protected]:#####.git (push)
we're expecting a match against git@<authority>:<owner>/<repo>, hence the failure
@RMacfarlane Doing a heroku git:remote --remote heroku -a <repo name> seems to have fixed it, thanks! Looks like I created the remote a while back using the Heroku CLI and it defaulted to the SSH remote.
This works:
$ git remote -v
heroku https://git.heroku.com/#####.git (fetch)
heroku https://git.heroku.com/#####.git (push)
@RMacfarlane any chance you can support at least parsing non-GitHub SSH remotes? One of my remotes is an SSH remote into my WSL instance on my windows machine and I'm continually getting the unable to parse remote error. My remote url is jkori@localhost:src/Avalonia.
my work stuff is ssh://(username)@(hostname-not-github):(portnumber) , and i'm constantly getting this error. IMO, the plugin should not even attempt to do anything with non-github urls?
Same here for remotes I have setup like so:
Unable to parse remote '<random-chars>@git.eu.platform.sh:<random-chars>.git'. Please check that it is correctly formatted.
fwiw, there is an option to disable an extension within a workspace, so i've had to use that for non-github code directories
@ericblade Well, in my case I'm getting these warnings for a repo with multiple remotes (one of which is Github.com). I don't want to delete the remote, and I can't disable the extension for non-Github remotes, so I'm a bit stuck.
also, it's not like this error comes up once, and you can dismiss it, and go on. it comes up constantly and even if you let it sit there and try to ignore it, it causes major lag.
Most helpful comment
my work stuff is ssh://(username)@(hostname-not-github):(portnumber) , and i'm constantly getting this error. IMO, the plugin should not even attempt to do anything with non-github urls?