Welcome
Your feature request related to a problem? Please describe.
I have used this github action, and noticed spurious failures when running the config verification (added in #1171 and enabled by default) when the schema cannot be downloaded from the default URL. The command permits specifying the schema to use via flag (https://github.com/golangci/golangci-lint/blob/main/pkg/commands/config_verify.go#L59-L66), which would allow the user to configure the linter to verify its config with a local copy of the schema.
Describe the solution you'd like.
I would like to add verify-with-schema: <file | url> as a config option. This would allow me to download a local copy of the schema and commit it to the repo, then use that frozen version of the schema to verify my config. Or I could host the config myself somewhere in my control.
Describe alternatives you've considered.
Right now I just set verify: false, which solves the problem of spurious failures.
Additional context.
See: #1331
Welcome
Your feature request related to a problem? Please describe.
I have used this github action, and noticed spurious failures when running the config verification (added in #1171 and enabled by default) when the schema cannot be downloaded from the default URL. The command permits specifying the schema to use via flag (https://github.com/golangci/golangci-lint/blob/main/pkg/commands/config_verify.go#L59-L66), which would allow the user to configure the linter to verify its config with a local copy of the schema.
Describe the solution you'd like.
I would like to add
verify-with-schema: <file | url>as a config option. This would allow me to download a local copy of the schema and commit it to the repo, then use that frozen version of the schema to verify my config. Or I could host the config myself somewhere in my control.Describe alternatives you've considered.
Right now I just set
verify: false, which solves the problem of spurious failures.Additional context.
See: #1331