Support for raw git URLs

[meysholdt]

it would be great if Gitpod could handle URLs for schemes http:// and https:// in exactly the same format as it is understood by git clone <git-url>.

We should evaluate if we can make https://gitpod.io/#<git-url> work or if this causes ambiguities with GitHub-URLs.

URLs that require password authentication or an installed SSH-key should be handled in separate issues.

[csweichel]

We'd need a way to identify if that's a raw Git URL. Two ways come to mind:

1. Introduce a special modifier, e.g. https://gitpod.io/#git/<git-url>
2. Try all other context parser first and if they can't handle the URL fall back to the Git parser (which in turn can attempt some magic to check if the URL actually is a Git repo).

The first option is easier, probably more reliable and more performant (in option 2 all wrong contexts might need to undergo HTTP requests to some wrong URL).
Option two is way nicer for users and closer to what one might expect.

[svenefftinge]

For github, gitlab and so on we can tell by the first segment what context parser to use. So we could possibly use the raw git for everything else.

[stale]

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.

[lukechu10]

Wouldn't this effectively make it possible to use private GitHub repos in the free plan?

[nurkiewicz]

Hi there! Any news on this issue? I can contribute or help in any other way in the development or testing

[rfay]

This seems like a great initiative. It would make some of the things we want to do with Drupal contribution so much easier.

AFAICT, the difference between a raw git URL and an explicit integration is that you can't do prebuild with a raw git URL and you have to either be expecting just to pull (which might be OK for many things) but if you wanted to push you'd have to have auth of one type or another.