See https://pkg.go.dev/cmd/go#hdr-Remote_import_paths specifically:
> The meta tag has the form: > <meta name="go-import" content="import-prefix vcs repo-root"> If you serve the meta tags over HTTPS on the package path, you can point it to the appropriate git repo On Wednesday, February 23, 2022 at 2:54:25 PM UTC+1 luxif...@gmail.com wrote: > Hello, > > In my company, we are planning to migrate to go modules. > The package name and VCS URL will be redacted for confidentiality. > > Our package name starts with `foobar.com/packagename` > <http://foobar.com/packagename> but the VCS URL to clone the repository > is `gitlab.corp.foobar.com/foobar-groups/packagename` > <http://gitlab.corp.foobar.com/foobar-groups/packagename>. > > We have more than 200 repositories containing multiple go packages, so a > package name rewrite is not an acceptable solution. > > What can I do for the migration? Can I use go proxy? > > Regards, > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/00fb2b93-2136-4dc1-8afb-b4ae9b0fb6bbn%40googlegroups.com.
