+- Cuberite Forum (https://forum.cuberite.org)
+-- Forum: Cuberite (https://forum.cuberite.org/forum-4.html)
+--- Forum: Development (https://forum.cuberite.org/forum-13.html)
+--- Thread: Move to GitHub (/thread-1192.html)
RE: Move to GitHub - NiLSPACE - 07-27-2013
You can still use TortoiseSVN to commit changes to the source. Also you can just checkout the source. The only problem I have is that loading the github website takes longer than the google code website on slow(mobile) devices.
RE: Move to GitHub - bearbin - 07-27-2013
Yeah, you can use github as a SVN repo, but everyone else can use git
The old MCServer projects are just people who have just checked it into github for some reason. Adding you to the repo.
Ok, I think everybody thinks it is good, and everybody should now agree that the new master is on github? Ok?
RE: Move to GitHub - xoft - 07-27-2013
@FakeTruth: Glad to see I'm not the only one who's NOT enthusiastic about Git
@all: Now we're in trouble, we have a GitHub repo and the old Svn repo and people are committing to the old Svn one. Now what? Can that still be migrated to GitHub, if we decide to move? (we haven't decided yet, have we?)
Also, can anyone write up a short guide on how to work with the GitHub repo, as a dev? Should I fork it and play on my own fork, or should I work on the upstream directly? And how will GitHub know that madmaxoft@gmail.com's svn commits are mine?
RE: Move to GitHub - bearbin - 07-27-2013
I believe github has a feature where you can set an alias for your account to solve the problem of it not knowing who you are.
The SVN changes can be ported across still, although not the other way around.
I'll get started on a guide for working with git. I think the best way for the workflow to work for us is for everyone to commit to the master repo, but NOT to teh master branch, instead to their branch or a feature branch, then submit a PR back to master and merge it in.
RE: Move to GitHub - xoft - 07-28-2013
I guess the move is official now, we're on GitHub now, so it's time to update all the links to the source and the bugtracker - in the wiki, in the forum redirect sections...
Is there any way to make the googlecode repo and FlySpray read-only?
RE: Move to GitHub - FakeTruth - 07-28-2013
I cannot make the googlecode repository read-online, but I can remove all members to make sure nobody can make a change.
I will then also update the main page with a notice and a link to the GitHub repository
RE: Move to GitHub - bearbin - 07-28-2013
I'm going to start work on transferring the wiki over, if it turns out good we'll have to see about that too.
It may not turn out to be as good, but we'll have to see.
RE: Move to GitHub - NiLSPACE - 07-28-2013
I think we can better keep the wiki that we have now.
RE: Move to GitHub - xoft - 07-28-2013
Agree, keep the current wiki
RE: Move to GitHub - xoft - 07-28-2013
So, generally this sums up as "bearbin wanted to contribute, so he made us move to github"