6 ms·
I can migrate my code, but not all my consumers which use "github.com/my/package" as the import qualifiers all over the place.
by rrix2 7y ago
I can migrate my code, but not all my consumers which use "github.com/my/package" as the import qualifiers all over the place.
- blocked_again 7y agoDoesn't setting up a mirror solve the issue ? https://help.github.com/en/articles/about-github-mirrors https://help.github.com/en/articles/about-github-mirrors
- brodock 7y agoGitHub doesn't provide you with any standard way to migrate the related metadata, but unlike Atlassian's Bitbucket, which doesn't make everything accessible with their APIs, it's possible to get all the data with GitHub's API (as of today). If you use GitLab importer tool, we migrate everything from your old project. All issues, all pull requests, and we even migrate inline comments inside a pull request. All it takes is one OAuth authorization and the pressing of a button. When inside GitLab, we even give you an Export zip file, that you can import in your hosted version of GitLab (or use any alternative, that can read our export file format).
- ChickeNES 7y agoI assume that's a reference to Golang? I gave up Go after one too many times dealing with its terrible package management
- int_19h 7y agoThat's exactly why any package versioning that hardcodes URLs to packages is broken by design. URL is where. A package is a what.