When trying to vendor this package into a bazel environment, tools.go package name "tools" is conflicting with the rest of the go files. This is due to the fact that gazelle generation largely ignores build tags in it's initial phase. Is there any way that file could either get the package matched or moved into it's own directory? Happy to make a PR for that either way...
When trying to vendor this package into a bazel environment, tools.go package name "tools" is conflicting with the rest of the go files. This is due to the fact that gazelle generation largely ignores build tags in it's initial phase. Is there any way that file could either get the package matched or moved into it's own directory? Happy to make a PR for that either way...