4 ms·
Given that git has such a distributed nature, couldn't you simply move over your code to Gitlab if and when Github actually is on the verge of shutting down? I
by sumitgt 9y ago
Given that git has such a distributed nature, couldn't you simply move over your code to Gitlab if and when Github actually is on the verge of shutting down?
I'm glad that Gitlab exists, however the lazy person in me sees no immediate need to use it. Even if all Github datacenters are destroyed by an asteroid, copies of repos I care about will still be around in enough people's computers to be able to recover.
- elmigranto 9y agoWhat about issues, wiki and other non-git data?
- mholt 9y ago(Nit: The GitHub wikis are also git repositories. https://help.github.com/articles/adding-and-editing-wiki-pages-locally/ https://help.github.com/articles/adding-and-editing-wiki-pag...) But anyway, the same argument could be made of an asteroid hitting your own datacenter with self-hosted GitLab instead.
- lloeki 9y agoIIRC GitLab can import GitHub issues straight from the UI.
- zegerjan 9y agoAlso PRs will be imported, milestones, labels and more: https://docs.gitlab.com/ce/user/project/import/github.html#overview https://docs.gitlab.com/ce/user/project/import/github.html#o...
- johannes1234321 9y agoThose can be extracted. Way more relevant imo: Links to your repo. For a mildly successful project a key part are external links pointing to your project. Those will point to a wrong location and you won't have control.