Comment by static_noise

8 years ago

Migrating from GitHub to GitLab

https://www.youtube.com/watch?v=VYOXuOg9tQI

this adresses some of the issues.

8 comments

static_noise

Reply
johannes1234321  8 years 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  8 years 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  8 years 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)

      2 replies →

  • jacques_chester  8 years 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.

  • lemming  8 years 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.