mirror of
https://github.com/tailscale/tailscale.git
synced 2026-03-28 00:31:51 +01:00
.github/workflows: limit vet to the tailscale.com module
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
This commit is contained in:
parent
34267d5afa
commit
2a192bba0b
2
.github/workflows/vet.yml
vendored
2
.github/workflows/vet.yml
vendored
@ -36,4 +36,4 @@ jobs:
|
||||
|
||||
- name: Run 'go vet'
|
||||
working-directory: src
|
||||
run: ./tool/go vet -vettool=/tmp/vettool tailscale.com/...
|
||||
run: ./tool/go vet -vettool=/tmp/vettool ./...
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user