[Rd] R-Forge > GitHub?
@|ngm@nn @end|ng |rom gm@||@com
Wed Jun 26 23:34:51 CEST 2019
Whereas it is true that one has to contact GitHub to detach a GitHub
repository, it really is no problem (or at least was no problem in 2016). I
wanted to do so when I took over the maintainer role of LaplacesDemon which
only remained on GitHub as a fork on some other person's private account.
So I forked and then contacted GitHub support and simply asked them to
remove the "forked form" reference on my new repository. They then quickly
detached my repository. As you can see, the "forked from" is gone:
In their response to my request they used the phrasing "Fork is detached."
which suggests that this is their preferred term for this step.
Am Mi., 26. Juni 2019 um 16:38 Uhr schrieb Lionel Henry <lionel using rstudio.com
> > On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.duncan using gmail.com>
> > 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
> 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.
> R-devel using r-project.org mailing list
Dr. Henrik Singmann
Assistant Professor, Department of Psychology
University of Warwick, UK
[[alternative HTML version deleted]]
More information about the R-devel