#golangci config
1 messages ยท Page 1 of 1 (latest)
@rocky plover heads up I'm going to push a small commit on top of that PR, dealing with corner cases in how the config file is passed
shouldn't conflict with the Severity-related changes
yeah i'm also still working on it, so just don't force-push ๐
are you touching the Report() function?
nah just fixing linting errors now
I can take that whole task if you'd rather focus on something else
This seems like something I can do
(and also I introduced the bug in the first place)
Anything left for you to push?
nope!
note, there's some weirdness with jobs that timeout on that pr, investigating that issue separately
Note: I'm going to keep the current behavior of disabling all overrides, but will setup the files in the container so that it's easy to change that
(this involves following the tool's recommendation of using $HOME/.golangci.yml as a default, hence my running into lack of env expansion and filing an issue about that
I'm still working on this, struggling with bad train internet