New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix support for ssh clones of kart repos. #40
Conversation
This moves the responsibility for determining the users intended clone source into the widget code. `kart@` and `http(s)://` paths are passed to the API, other paths are assumed to be file system paths.
Shouldn't Kart have that responsibility? One issue... file protocol isn't the same as a file path: We're also missing |
This is a heuristic to interpret the input into the "URL of repository to clone" input. It seems appropriate for the widget to do it.: I would expect Kart to be more explicit.
Should it strip the |
No, the reason for adding it is that, if the |
aha. This is a Git thing, not a Kart thing. So without the → I don't think % progress is worth the extra slowness - mostly people will use ssh/https remotes and see the progress. We could get progress on the working copy population phase, currently there isn't any but that is in Kart's control. |
As it stands, SSH clones don't work at all, which is what I'm was seeking to fix. This doesn't change the existing file system handling though, perhaps that should be a separate issue? |
We need to drop all the prefixing IMO and hand it off to Kart |
Will it break file based clones if the progress dialog doesn't work? |
No, it won't break anything to remove the prefixing. I will merge the PR, so ssh clones work fine, and then remove the part that adds the fil:// prefix |
The plugin currently fails to recognize SSH paths to hosted repositories.
This change moves the responsibility for determining the users intended clone source into the clone widget. This also fixes handling of paths already prefixed with
file://
and tightens up the checking of http/https paths.