Go is moving to GitHub

I think this is Google quietly admitting that Google Code is all but dead. They will not completely get rid of it, but I would not be surprised if they switch it to read only mode sometime soon.<p>This is a momentous move for Github, especially with Microsoft moving .NET to Github as well. As someone who loves Github immensely, this makes me happy knowing that my favourite service is going to be around for a very long time.<p>Kudos to the Github team for well and truly making it as the premier code hosting and collaboration tool for developers and lovers of open source. It only goes up from here.

Google hosting Go on GitHub. Microsoft hosting .NET on GitHub. It must feel like an accomplishment to be implicitly endorsed by these companies.<p>Considering open source&#x27;s history, you&#x27;d think its primary management tool would be open source as well. I guess it&#x27;s GitHub&#x27;s combination of accessible design + performant version control + lack of ads + reliability that made it the premium source for anything open source.<p>I&#x27;m impressed.

This is a huge compliment to GitHub, for Google to be moving one of its premier open source projects off of Google Code and onto GitHub.<p>More importantly, though, this is a significant compliment to the Go community, for Go to uproot itself and move to where the majority of its users are.

The writing&#x27;s on the wall for Google Code. I don&#x27;t think I&#x27;ve seen a new feature in several years.

I think these are two separate issues:<p><pre><code> 1) Go is moving from Google Code to Github 2) Go is moving from Mercurial to Git </code></pre> To echo another user in the thread: &quot;am I the only one who prefers Mercurial to Git?&quot; In my view Mercurial is on par or even superior to Git, but lacks &quot;Linus made it&quot; fame. Too bad... I have used both Mercurial and Git and find hg command line interface much more intuitive to use. As for GUIs, there really isn&#x27;t much difference between the two (too bad GitHub only supports git though).

It is great to see so many projects moving to git and GitHub in particular. GitHub is incredibly helpful for quickly taking a look at a project and figuring out what areas of a project are still evolving and being actively developed.

Google Code has a really bad user interface. This migration makes sense. I wish they stuck with Mercurial and moved to Bitbucket instead, but Github is still better than Google Code.

Now all we need is Jeff Bezos to buy Github :-) That would be funny.<p>But on the story this is a great move, Github is much nicer than Google Code and more actively supported. I had not heard of Gerrit before and that was a really pleasant discovery. Now to figure out how to get that setup at the office.

It is so sad that Google Code has not been given some love. Their bug tracker is far, far superior to Github. The review mechanism is also quite, quite good (Gerrit I presume). The UX was too, too Sourceforge-ish and could not compete with Github or (what I think is best of breed) Bitbucket.

Props on the move, it shows that golang is flexible to make moves for what&#x27;s best for the community rather than stick it out in google code. I hope this results in benefits to the iteration cycle.

I was hoping for this transition for a long time! Github is far more accessive and user-friendly than the Google repositories. Great move.

Does anyone know what code review system they are using with github?

I think this move is great for 2 big reasons:<p>1. This fits better with the workflows I know and are common for Go programmers. I use Github and Git regularly for a variety of things, and I only ever use Google Code and Mercurial for things dealing with the Go source or tool repositories. Along with the change of the much of the compiler source code from C to Go, this will make it a lot easier to get involved with the core of Go.<p>2. Simplifies using import paths for Go&#x27;s tools. There&#x27;s a bunch of different repositories in Google Code&#x27;s Go project, and using them is slightly more painful because Go Get then requires mercurial to work. Reducing developer friction is a good thing, especially in odd places such as when a github repository uses a Google code repository and suddenly you need mecurial to import something using git.

As someone who uses Ruby as my primary language; I&#x27;m totally jealous of this move. While there is a github mirror, it sucks having to use Subversion for the &quot;one true repo&quot; when everything else I work with these days is on git.

&gt; <i>The world today is quite different from the world then.</i><p>Not really. Everyone used Git and Github 5 years ago too. That&#x27;s why it was so annoying that Go chose to use Google Code for everything, although not surprising considering it&#x27;s a Google project.

Hi Go team,<p>if you want an alternative for Gerrit code review, you can also use <a href="http://review.ninja" rel="nofollow">http:&#x2F;&#x2F;review.ninja</a>. It&#x27;s also open source, so you are welcome to contribute.<p>Cheers, Mitch

I’m concerned that it won’t get any stars.

I guess its official, misogyny is ok in our industry.<p>Have we forgotten about: <a href="http://lmgtfy.com/?q=github+misogyny" rel="nofollow">http:&#x2F;&#x2F;lmgtfy.com&#x2F;?q=github+misogyny</a> ?<p>I&#x27;m not sure github even experienced a dip in traffic.<p>There are github alternatives, it took me 30 minutes to remove my github subscription and migrate my repos to bitbucket.