Comment by monotypical
8 years ago
Changing the remote doesn't migrate anything in the issue tracker, merge requests, webhooks, pages or wiki
8 years ago
Changing the remote doesn't migrate anything in the issue tracker, merge requests, webhooks, pages or wiki
Migrating from GitHub to GitLab
https://www.youtube.com/watch?v=VYOXuOg9tQI
this adresses some of the issues.
It doesn't solve the number one issue: External references to your project will all still point to github.com since that's where the project homepage (aka README.md) is.
If GitHub does get sold to MS and I end up moving to GitLab, I'll probably push one last commit to the GitHub repo adding a header saying the project has moved, with a link to the GitLab repo. It's not perfect, but it wouldn't be too bad.
3 replies →
I expect Google could be convinced to accept certain files or metadata in a README as equivalent to a 301 permanent redirect, meaning searches will remain effective. That would account for a lot, especially if Chrome begins to honour it.
Actually, the #1 issue is that everyone can easily file an issue/contribute in other ways at Github without having to create another account to do so.
1 reply →
I seem to remember that under the GDPR, vendors have to make data exportable. I wonder if people could use that for GitHub issues and the Wiki.
GitHub pages is super easy to move except for getting users to know the new domain.
The GDPR only applies to personal data, which won't be most of the content on GitHub.
Anyway, there are APIs which one can use to export issues.
Personal data is extremely broad and is any data that can be identified to an individual. If my photos are Facebook are personal data, then so is my code on GitHub (even if some people are professional photographers or programmers).
It wouldn't be seamless. But it wouldn't be difficult for a competitor to create a "competitor import" feature that moved over most of it in a few clicks.
It's possible, but I think it's a stretch to say it "wouldn't be difficult."