Why Your Go Private Modules Shouldn't Use Raw GitHub Paths
A Real Nightmare Last year, a friend of mine — let’s call him Alex — made a perfectly reasonable decision: migrate his company’s code from GitHub Enterprise to a self-hosted GitLab instance. Sounds straightforward, right? Move the repos, tweak the CI, and call it a day. Until they realized: all 200+ Go microservices had import paths starting with github.com/their-org/. Moving the repositories took a weekend. But updating the import paths across every downstream service? Three engineers spent two weeks on it. Then another week for regression testing. ...