����� Thanks.� I'm still having problems:
��� ������� 1.� I went to "github.com" and logged in with my standard GitHub account ��� ������� 2.� Then I clicked "+" in the upper right, just left of my GitHub ID icon, and selected "Import a repository", as Lionel suggested. ��� ������� 3.� " Your old repository�s clone URL" = "https://r-forge.r-project.org/projects/ecdat/"; with "Name" = "Ecdat". ��� �� �� ������� ** >> This failed, first giving me a 500 failure code, then reporting " Repository creation failed."� When I tried it again, I got, "The repository Ecdat already exists on this account." ����� What do you suggest I try next? ����� Thanks, ����� Spencer On 2019-06-26 12:02, Lionel Henry wrote: > I think all 3 issues are solved by: > > 1. Use the "+" button on github.com <http://github.com>�and select > "Import a repository". > 2. Pass the URL of your SVN repo. > > Lionel > >> On 26 Jun 2019, at 18:58, Spencer Graves <spencer.gra...@prodsyse.com >> <mailto:spencer.gra...@prodsyse.com>> wrote: >> >> ����� Thanks to Duncan, Lionel and Henrik for their quick replies. I >> have further questions: >> >> >> ��� �� ���� 1.� Will GitHub automatically transfer the commits I made >> to R-Forge in the past couple of days? R-Forge is now at Rev. 420, >> and GitHub is still at 418. Will 419 and 420 be automatically >> mirrored onto "https://github.com/rforge/ecdat"; sometime in the next >> 24 hours or so?� Is there something easy I can do to force that update? >> >> >> ��� �� ���� 2.� Is there a way to make this GitHub version the >> master?� It currently says it is a 'Read-only mirror of "ecdat" from >> r-forge SVN.'� I can probably change >> "r-forge.r-project.org/projects/ecdat >> <http://r-forge.r-project.org/projects/ecdat>" so I'm the only one >> authorized to make changes there and then stop committing changes >> there.� However, before I do that, I'd want to make sure I can commit >> directly to the GitHub version, etc. >> >> >> ��� �� ���� 3.� How can I make myself the owner and a contributor for >> the GitHub version?� I'm a "Project Admin" on the R-Forge version, >> but currently no one can make any changes to the GitHub version >> except via R-Forge.� There must be a recommended migration process. >> >> >> ����� I could create a separate version of this package on GitHub, >> but all the history would be lost. >> >> >> ����� Thanks again, >> ����� Spencer Graves >> >> >> On 2019-06-26 10:35, Lionel Henry wrote: >>>> On 26 Jun 2019, at 17:25, Duncan Murdoch <murdoch.dun...@gmail.com >>>> <mailto:murdoch.dun...@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 >>> <http://github.com> and select >>> "Import a repository". This supports both git and svn repos. >>> >>> Best, >>> Lionel >> > [[alternative HTML version deleted]]
______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
