From ||one| @end|ng |rom r@tud|o@com  Wed Jun 26 17:35:21 2019
From: ||one| @end|ng |rom r@tud|o@com (Lionel Henry)
Date: Wed, 26 Jun 2019 17:35:21 +0200
Subject: [Rd] R-Forge > GitHub?
In-Reply-To: <8d6c6dd4-d231-ecc7-c584-6e08f93a81e5@gmail.com>
References: <71f66de5-e1aa-5649-b07a-6cf79f9b07bc@prodsyse.com>
 <cb4218b1-7fcc-80cb-18ab-361b93a3177e@prodsyse.com>
 <8d6c6dd4-d231-ecc7-c584-6e08f93a81e5@gmail.com>
Message-ID: <89645BC9-C6BF-4E57-8AA0-9F426BA8AC5E@rstudio.com>


> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan at gmail.com> wrote:
> 
> R-Forge is mirrored on Github; see https://github.com/rforge/ecdat, for example.  That shows 418 commits in its history; presumably that's the full R-forge history.  I think that's newer than Michael Friendly's gist.
> 
> So I suspect (but haven't tried to do this) that migration now is as simple as doing a Github fork to your own Github account, and then basically forgetting about the R-forge stuff, or deleting it (and I don't know how to do that).

I think it's better to avoid the Fork button in this case, because forks are
treated specially in the Github UI. In this case you'll want your repo to
appear as a main repo, and not a fork. AFAIK the only way to unfork a repo
is to ask the Github staff to do it.

So instead of forking, use the "+" button on github.com and select
"Import a repository". This supports both git and svn repos.

Best,
Lionel


[Rd] R-Forge > GitHub?
Lionel Henry