What is the issue?
When I configure skipLint with a set of folders dagger check go:lint-all ignores that setting and lints all projects. Is this intended behavior? In repositories were you have projects you don't think should be linted, either they don't matter and you don't want to spend any cycles fixing them, are too old and can't yet be deleted or something else its necessary to have a way for go to permanently ignore those projects. Using dagger call go --skip-lint works as expected.
Dagger version
dagger v1.0.0-beta.3 (image://registry.dagger.io/engine:v1.0.0-beta.3) linux/amd64
Steps to reproduce
Configure skipLint for any go module in a repo and run dagger check go:lint-all. The trace will show that skipped projects will be linted.
Log output
Example trace: https://dagger.cloud/dagger/traces/8d7cf03f5d7f7541941b27396962bbb3 (this is a private trace)
What is the issue?
When I configure
skipLintwith a set of foldersdagger check go:lint-allignores that setting and lints all projects. Is this intended behavior? In repositories were you have projects you don't think should be linted, either they don't matter and you don't want to spend any cycles fixing them, are too old and can't yet be deleted or something else its necessary to have a way forgoto permanently ignore those projects. Usingdagger call go --skip-lintworks as expected.Dagger version
dagger v1.0.0-beta.3 (image://registry.dagger.io/engine:v1.0.0-beta.3) linux/amd64
Steps to reproduce
Configure
skipLintfor any go module in a repo and rundagger check go:lint-all. The trace will show that skipped projects will be linted.Log output
Example trace: https://dagger.cloud/dagger/traces/8d7cf03f5d7f7541941b27396962bbb3 (this is a private trace)