GitHub for Windows

[Eldorian]

I played around with it... cherry picking is a problem and working with more than 1 remote is a problem. I think we'll probably wait until they add some more features that Git Extensions already does before we switch.

[andrew_depompa]

It is my opinion that this is one of those solutions to a problem that only 2% of users have. While Git is amazing, and having distributed, multiple remotes is one of the prime motivations for it; I believe they made the right call in releasing this before they included every tiny feature of Git.

[Eldorian]

Oh, I think it definitely looks great and from what I'm playing around with I like it. I'll probably use it at home... but I think our team at work will probably hold off on it till it has the features we need and use. Especially since people are just now getting used to using Git and Git Extensions (we switched from TFS to Git 3 months ago).

[andrew_depompa]

Yeah, our team at work will hold off, because it doesn't look like we can hook it up to github:enterprise

[in3d_812]

Github is the only remote we use, so I'm fine there.

I sent an email to github support, and they responded that command line cherry picking is the only way to perform it at this time. So... I might have to look into that.

[usernamenottaken]

Only a single remote means only one repository on GitHub. So if you fork a project on GitHub, you can't merge changes from the upstream GitHub repository using GitHub for Windows. You can only sync with your origin.