Libgdx is now on Github (sorta)
Our transition to Git is complete. The projects are all in a good shape, the build server works off of git (had to massage the scripts a little to create empty dirs). Here’s the summary of relevant changes.
- The code itself is hosted on Github now. All branches and tags are there too, as well as the entire commit history.
- The issue tracker and wiki stay on Google Code. If you file an issue containing a patch, you can now create a pull request on Github, and post an issue on our tracker with a link to the pull request.
There’s currently a problem with Google Code that prevents us from hosting our code there. You can star the corresponding issue if you like. Once that issue is resolved we might go back entirely to Google Code, i’m not sure about that yet.
The wiki and the issue tracker stay on Google Code, the corresponding features on Github have been disabled. You can still send us pull requests there though! Just make sure to also file an issue in that case.
The only downer is the repo size. This is due to the binaries we added and removed to the SVN repo over the life-time of libgdx. There are ways to remedy this, we have an expert at our disposal that promised to help us with that. This will most likely involve a rebase, which might get ugly. We’ll see and stick to what we have now for the moment.
Hope everybody enjoys this move. Next up: pushing artifacts to SonaType for you Maven guys. Our build will stay ant, core development environment will stay Eclipse for the time being. I had enough fun with the Git transition
Nate’s edit: After using TortoiseGit for about a year and trying github’s app for about 10 minutes, I find both to be extremely lacking. I tried Git Extensions, but I don’t like it much either. I guess SmartGit is next.