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.

  • mingming-killer

    I use Git Bash Shell in Git Extensions in window, it’s work well. It’s great use Git to replace SVN. ^_^

  • Robert massaioli

    Excellent! One pull request already submitted. Another one coming soon!

  • Varriount

    For is the only system I’ve had ever where the console is easier to use than the gui.

  • Semtiko

    Why not EGit (JGit)? I think it’s better, than standalone software.

  • Rouman

    I use eGit at work (Eclipse Plugin), it’s pretty cool.

  • Erlend Sogge Heggen

    We’ve been evaluating Git/GitHub for jME as well. Thanks for sharing your progress.

    Regarding Git clients, GitHub recently explained a way to keep using GitHub with your favorite SVN client, for those who aren’t quite convinced by any of the Git clients out there:

  • Mario

    Hey, that’s a great resource, thanks Erlend. I guess it can make the transition for old farts like Nate easier.

  • impaler

    For anyone using macs and want a good client, try:

    Good move guys, I prefer git to SVN lately.

  • Mats

    I really like the move to Git. And to github as well, taking a quick look at code there is sooo much easier than on google code.

    Nate, if you are using windows, you can check out but may be lacking as well. I find that most advanced stuff is easiest to do through the command line. For day-to-day normal usage I usually use the git plugin to IntelliJ, which covers all my needs.

  • Mario

    Github’s App seems to be geared towards Git newcomers with very lightweight usage patterns. Lots of things are sadly a bit terribu and for a large project like libgdx, it’s just not up to par. We settled on a mixture of cli and SmartGit for now, the later is not all that bad (not free for non-commercial use though!).

  • mxttie

    On windows I also use the git bash or simply the git support in Intellij.