The recommend approach caching go modules is to create a ".go" directory in the top level of a project. See: https://docs.gitlab.com/ee/ci/caching/#cache-go-dependencies
go test, go vet, go list and staticcheck ignore this directory because is starts with ".". We use goimports within our pipeline. I'd like to not include ".go" in the directories scanned, as this leads to pipeline failures and is slow. What's the best way to handle this at the moment? And I'm also curious if there's a reason why goimports behaves differently to other go tools. -- 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/cc24e232-494c-4b8e-a967-1f0d363a5dfdn%40googlegroups.com.
