You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A warning the the import path may be incompatible with Go modules. For example:
$ go mod init github.com/terinjokes/go-mod-init-demo
go: warning latest tag is v2.1.0, but module not have a /v2 path. This may prevent others from importing your module.
go: creating new go.mod: module github.com/terinjokes/go-mod-init-demo
The phrasing is just for an example. I recognize there may be several edge cases in accurately detecting the scenarios and intents of users, but I've seen many projects migrate from vendoring while already at a >= v2 release, and not realize they've made their project difficult to import.
What did you see instead?
$ go mod init github.com/terinjokes/go-mod-init-demo
go: creating new go.mod: module github.com/terinjokes/go-mod-init-demo
The text was updated successfully, but these errors were encountered:
terinjokes
changed the title
cmd/go: mod init provides not version warnings
cmd/go: mod init has no version warnings
Mar 3, 2020
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I create a git repository where the latest tag is >= v2, then ran
go mod init
What did you expect to see?
A warning the the import path may be incompatible with Go modules. For example:
The phrasing is just for an example. I recognize there may be several edge cases in accurately detecting the scenarios and intents of users, but I've seen many projects migrate from vendoring while already at a >= v2 release, and not realize they've made their project difficult to import.
What did you see instead?
The text was updated successfully, but these errors were encountered: