Closed
Description
Welcome
- Yes, I'm using a binary release within 2 latest major releases. Only such installations are supported.
- Yes, I've searched similar issues on GitHub and didn't find any.
- Yes, I've read the typecheck section of the FAQ (https://golangci-lint.run/usage/faq/#why-do-you-have-typecheck-errors).
- Yes, I've tried with the standalone linter if available (e.g., gocritic, go vet, etc.). (https://golangci-lint.run/usage/linters/)
Description of the problem
getting this error this morning in our CI, thing works properly when building with -buildvcs=false, i am not sure how to pass that flag to golangci-lint
+ make lint-go
Linting go files...
cmd/pipelines-as-code-controller/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
package main
cmd/pipelines-as-code-watcher/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
package main
cmd/pipelines-as-code-webhook/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
package main
cmd/tkn-pac/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
package main
make: *** [Makefile:75: lint-go] Error 1
Version of golangci-lint
% docker run -it mirror.gcr.io/golangci/golangci-lint:latest golangci-lint --version
golangci-lint has version v1.54.1 built with go1.21.0 from a9378d9b on 2023-08-11T13:17:35Z
Configuration
Go environment
docker image
Verbose output of running
cmd/pipelines-as-code-controller/main.go:1: : error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping. (typecheck)
package main
A minimal reproducible example or link to a public repository
https://github.com/openshift-pipelines/pipelines-as-code
Validation
- Yes, I've included all information above (version, config, etc.).