Community
Participate
Working Groups
Since GitHub is one of the main reasons to use Git, it's quite likely that one of the first ports of call will be GitHub. However, Git shows incorrectly formatted URLs for the read-write support links; they show, for example: git@github.com:alblue/EGit.git This isn't a valid URL and so doesn't get parsed by the Clone wizard. Instead, we have to change it to: git+ssh://git@github.com/alblue/EGit.git Whilst this may be obvious for long-time Git users (and the command line may do the translation automatically) it may be a dissuading factor for novice users. There is a question of whether we want to support site-specific hacks - but arguably GitHub's (current) domination may swap that decision.
As pointed out by Christian (at http://egit.eclipse.org/r/#change,910), these are rsync/scp like protocols and not URLs specific to GitHub. So we should support those as well. http://www.kernel.org/pub/software/scm/git/docs/git-push.html#URLS An alternative scp-like syntax may also be used with the ssh protocol: [user@]host.xz:path/to/repo.git/ This should be functionally equivalent to ssh://[user@]host.xz/path/to/repo.git/
merged as 2160c09dd4f678c5f2f8e730945be637210b39de
