Re:Why GitHub’s pricing model stinks (for us)
by why-el on Wednesday February 13, 2013 @07:30AM
(#5212708)
Yep, this is exactly what I do. Though I will start collaborating on a private project beginning June and I am not sure how Bitbucket fares in that regard? Any experience with that?
Re:Why GitHub’s pricing model stinks (for us)
by Hates_ on Wednesday February 13, 2013 @07:57AM
(#5212817)
I'm collaborating on some projects on Bitbucket and it has pretty much everything you need. It doesn't have some of the nice little touches that Github has like autocomplete emoji etc, but nothing that wouldn't make me miss Github if I had to move over to it 100% for private repos.
And I don't miss Github's collaborative features in my private repos because I'm not collaborating in those :) Bitbucket is literally just "a place to push my repo where it'll be safe" for me[1]; Github is "a place where I can collaborate with others."
And you know what? You can even use both for a single project. Push your public branches to Github, accept patches, then base a private product on the result [just some extra non-pushed-to-public branches] and work on that in Bitbucket. For example, you could have, say, the Chromium codebase on Github, and then Chrome on Bitbucket.
[1] Well, okay, Bitbucket is also pretty good for doing deploys from: you can CNAME git.yourcompany.com to them, set up some Deploy Keys and Deploy Hooks, and it'll feel just like you had your own internal repo server for your deploy server to talk to.