6 ms·

Changing the remote doesn't migrate anything in the issue tracker, merge requests, webhooks, pages or wiki

Y7ZCQtNo39 8y ago
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.
- t_treesap 8y ago
  It's possible, but I think it's a stretch to say it "wouldn't be difficult."
static_noise 8y ago
Migrating from GitHub to GitLab https://www.youtube.com/watch?v=VYOXuOg9tQI https://www.youtube.com/watch?v=VYOXuOg9tQI this adresses some of the issues.
- johannes1234321 8y ago
  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.
  - mort96 8y ago
    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.
    - johannes1234321 8y ago
      Until MSFT/GitHub does what Sourceforge.net did - taking over project sites from projects which moved away and adding malware (adware/spyware) into those ;) (I believe with all critique on Microsoft they aren't as bad, but want to exemplarize the risk)
      - suby 8y ago
        This would be a great way for them to accelerate migration away from Github.
      - askvictor 8y ago
        It might just be cleaner to close the github repo and when other projects find a 404 where it used to be, they'll have to use super detective skills (i.e. Google it) to find the project's new home. And if they can't find it that way, then nothing of value was lost. (Yes, yes, I know it's more nuanced than that, but if you wanted permanence, you'd be hosting on your own domain, right?)
  - lemming 8y ago
    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.
    - st1ck 8y ago
      You can sign in with your Github account to gitlab.com.
  - jacques_chester 8y ago
    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.
slaymaker1907 8y ago
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.
- Symbiote 8y ago
  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.
  - dannyw 8y ago
    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.

t_treesap 8y ago
It's possible, but I think it's a stretch to say it "wouldn't be difficult."

static_noise 8y ago

Migrating from GitHub to GitLab https://www.youtube.com/watch?v=VYOXuOg9tQI https://www.youtube.com/watch?v=VYOXuOg9tQI this adresses some of the issues.

johannes1234321 8y ago
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.
- mort96 8y ago
  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.
  - johannes1234321 8y ago
    Until MSFT/GitHub does what Sourceforge.net did - taking over project sites from projects which moved away and adding malware (adware/spyware) into those ;) (I believe with all critique on Microsoft they aren't as bad, but want to exemplarize the risk)
    - suby 8y ago
      This would be a great way for them to accelerate migration away from Github.
    - askvictor 8y ago
      It might just be cleaner to close the github repo and when other projects find a 404 where it used to be, they'll have to use super detective skills (i.e. Google it) to find the project's new home. And if they can't find it that way, then nothing of value was lost. (Yes, yes, I know it's more nuanced than that, but if you wanted permanence, you'd be hosting on your own domain, right?)
- lemming 8y ago
  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.
  - st1ck 8y ago
    You can sign in with your Github account to gitlab.com.
- jacques_chester 8y ago
  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.

slaymaker1907 8y ago

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.

Symbiote 8y ago
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.
- dannyw 8y ago
  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).