Dominik Honnef ec55db560e Don't require relative paths to start with ./ or ../ ... Errors reported by Go, even when containing relative paths, do not always begin with ./ or ../ – for example: $ go build ./... # honnef.co/go/tools/lintcmd lintcmd/format.go:28:8: syntax error: cannot use path := filepath.Clean(pos.Filename) as value We could require either ./, ../ or at least one path separator and still match Go's output. However, commonly used linters (such as Staticcheck and golint) never use ./ for relative paths. Their output stopped being matched when we moved from v1 to v2. I believe that being able to match the output of linters is worth relaxing the pattern for. This change slightly relaxes the stricter pattern that was introduced as part of v2 to address #46. However, the pattern is still stricter than it was in v1 and as strict as it can be for most users.		2021-01-16 04:49:09 +01:00
..
data	Use GitHub releases to download Go versions. (#58)	2020-06-29 11:41:13 -04:00
setup-go.test.ts	Don't require relative paths to start with ./ or ../	2021-01-16 04:49:09 +01:00
verify-go.sh	Use GitHub releases to download Go versions. (#58)	2020-06-29 11:41:13 -04:00