← Back to context

Comment by dewey

3 hours ago

> That is, if you move your git hosting to GitLab then you have to change your code!

You can also just use "replace github.com/example/example => gitlab.com/example/example" in your go.mod file and everything will keep working. That seems like a very pre-mature optimization for something that doesn't really matter.

9 comments

dewey

Reply
furyofantares  1 hour ago

Yeah, I think putting github.com in your repo is a mistake but it seems massively overstated. Seems trivial to fix all the code, or to just use go.mod, or first use go.mod and then fix your code.

kelnos  1 hour ago

What about everyone else using your code? You are going to ask them all to update their code as well? Many of them probably won't realize, and will get stuck on an old version that never gets updated, even to fix bugs and security issues.

  • jayd16  1 hour ago

    By this logic, those folks should be pointing to their own hosted mirrors of the project, no?

peesem  1 hour ago

why not just use replacements to begin with if you don't want to bother with setting up domains?

"replace example => github.com/example/example" at first, then change to "replace example => gitlab.com/example/example" or similar when there's a migration

(i don't use go, but i hope this is possible and i am confused if it's not)

mort96  3 hours ago

And you'll just leave references to abandoned infrastructure in your code forever?

  • cyberpunk  2 hours ago

    cmd+shift+r in goland, push to a branch, open a PR, ask devops to make the old location archived and prevent further writes. After a couple months remove access to the old one and see what breaks.

    You know, normal development task, small amount of story points..