3 ms·
The switching costs away from Github is trivially low actually. You may lose out on some of the niceness related to github - but there are plenty of good git ba
by nullspace 12y ago
The switching costs away from Github is trivially low actually. You may lose out on some of the niceness related to github - but there are plenty of good git based source code hosting software out there.
- k-mcgrady 12y agoThe only pain point in switching I can think of is issues/wiki. Are they exportable from GitHub and importable into something like BitBucket?
- icehawk219 12y agoThe wiki is just a Git repository so you could just clone that and then do what you need to with it. Once it's cloned locally I'd imagine it's fairly straight forward to either manually copy it to something else or use an API to copy the files up to a wiki somewhere. For issues GitHub has great API coverage for fetching them [0] so I'd imagine it's not terribly difficult to write a migration script. There are already ones out there for going from BitBucket to GitHub [1] so the reverse should be possible. [0] https://developer.github.com/v3/issues/ https://developer.github.com/v3/issues/ [1] https://github.com/vbabiy/bitbucket_issue_migration https://github.com/vbabiy/bitbucket_issue_migration
- jmnicolas 12y agoI should have been more clear about what I meant : I was thinking of failing as in downtime not the company being bankrupt. Imagine a cyber-attack that would paralyze Github for one month ...