diff options
| author | Tom Proctor <tomhjp@users.noreply.github.com> | 2026-03-23 16:56:08 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-03-23 16:56:08 +0000 |
| commit | db3348fd25005e35a3eaa21583a1a7e6100893e9 (patch) | |
| tree | 599bd2ea97fc232a7f94c5cc1841fedf73b2995b /control/controlhttp/controlhttpserver | |
| parent | 18528d1dd95dd3a16a294d1bd0ee2f79a23f6bb3 (diff) | |
| download | tailscale-db3348fd25005e35a3eaa21583a1a7e6100893e9.tar.xz tailscale-db3348fd25005e35a3eaa21583a1a7e6100893e9.zip | |
.github/workflows: limit vet to the tailscale.com module (#19084)
This repo's module is tailscale.com, and the tailscale-client-go-v2 repo
uses tailscale.com/client/tailscale/v2. It seems from #19010 that if we
have the client module as a dependency in this module, go vet will start
to consider the client module as part of tailscale.com/...
I'm not sure if this is a bug in go vet, but for now let's take the easy
fix and specify ./... instead. In my testing, it seems like this is
sufficient to make sure it just walks the file hierarchy and doesn't
find the client module as a sub-path.
Updates tailscale/corp#38418
Signed-off-by: Tom Proctor <tomhjp@users.noreply.github.com>
Diffstat (limited to 'control/controlhttp/controlhttpserver')
0 files changed, 0 insertions, 0 deletions