-
Notifications
You must be signed in to change notification settings - Fork 123
github remotes not supported #560
Comments
For the remote, the problem is: that's a different git authentication method. Quite likely ssh authentication will work where https doesn't (and vice versa). |
Yeah, I think it's a ssh syntax. The question is, if we just store it in a string and then feed it back to |
Otherwise the plan would be to manually specify the two separately, e.g. |
So if you prefix it with This doesn't make everything work, but it's a start. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
If I run with
repo C:\Code\JustEat.StatsD
this should inspect the local repo and find the remotes.But I get
This is because there are remotes with e.g. name: "origin" and "url":
git@github.com:AnthonySteele/JustEat.StatsD.git
And this cannot be cast as
Url
- it is not a http(s) url, although it is a format that github uses a lot.It's clearly not a simple fix since a run for
repo git@github.com:AnthonySteele/JustEat.StatsD.git
fails similarly.Do we try to convert these to the corresponding http urls (in this case
https://github.com/AnthonySteele/JustEat.StatsD
) or try to work with them as is?The text was updated successfully, but these errors were encountered: