OK. I'll just point out that if the repo contains a set of related packages, then normally you'd only put a go.mod at the top level.
For an example of this in action, see the "testify" group of packages: https://github.com/stretchr/testify/ The subdirectories are separate packages. For example I can do import ( "github.com/stretchr/testify/assert" "github.com/stretchr/testify/require" ) ... assert.NotEqual(t, 1, 2) require.True(t, true) However, you'll see there's no go.mod in the package directories. They are anchored to the go.mod at the root. -- 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/dcbab28e-e335-4cac-bd7d-8702efd4ab27n%40googlegroups.com.
