Google Code is officially dead; here’s how to transfer your projects to GitHub


coder coding developer development

The day has finally come — Google Code is dead. The service, a code repository for developers to host their open-source projects, simply wasn’t able to adapt to the growing needs of developers like GitHub has been able to. Google apparently wasn’t interested in trying to contend, either (in fact, they admitted they’d already moved a significant amount of their own projects to GitHub as they “wanted to be where the developers are”).

Here’s a quick timeline on what’s going down:

  • March 12, 2015 – New project creation disabled.
  • August 24, 2015 – The site goes read-only. You can still checkout/view project source, issues, and wikis.
  • January 25, 2016 – The project hosting service is closed. You will be able to download a tarball of project source, issues, and wikis. These tarballs will be available throughout the rest of 2016.

We suggest that you don’t wait until the final gong tolls — might as well start moving all your digital goods over to GitHub as soon as possible. Thankfully Google has a handy tool to make that as easy as a few clicks.

[via Google]

Quentyn Kennemer
The "Google Phone" sounded too awesome to pass up, so I bought a G1. The rest is history. And yes, I know my name isn't Wilson.

Google could be working on a built-in VPN service for use on open WiFi networks

Previous article

HTC One M9’s first official release date is March 16th

Next article

You may also like


  1. Github has it’s uses and value and has been heavily adopted, but man, it is an utter confusing PITA if you actually have to work with it and on it. So many steps and effort and at times, several apps needed (Github app, terminal commands, Github website open, etc.). I dread it when I have clients that need me to work in GitHub. So cumbersome and at times, esoteric. As a developer, I hear 1 specific lie over and over from the IT guys I work with…. “oh, once you use it you will ask yourself how you ever lived without it”. Bah, years later and many brainwashed comments like that and… I hate using it still. But again, I understand it’s value. But it needs streamlining.

    1. It’s OK if you don’t like git, but any dev worth a damn MUST use some type of revision control system. The older alternatives like cvs, svn, and mercurial are crap, but if you’re used to ’em it’s the devil you know.

      1. Depends… depends on the size of the project and the number of players involved. Before Git, what did we do? We communicated and no ones code got eaten.

        Now, based on the number of IT guys from different companies I have had to work with in Git, some big some small, I started to notice a trend where they really wanted to use Git in scenarios where it was not needed. But, it was more like they wanted to be able to claim and say they used Git.

        Anyhoo… again, I get the value and importance of it and the need for it in some, not all, cases. And compared to most offerings, it is “better” – but when I have 3-4 apps and processes and steps and esoteric command line codes to run to make 1 change that would otherwise take 15 seconds on an FTP server; it is time to consider bloat and the inefficiency of the system.


          It has a name: Visual Source Safe. If you’ve never used it (or even heard of it) consider yourself lucky.

  2. Huh, competition reduces.

  3. Dear god. I can’t unsee that horribly insecure (and deprecated) call to PHP’s old `mysql_connect()` function. My eyes!!!!

Leave a reply

Your email address will not be published. Required fields are marked *

More in News