golangci-lint | Fast linters Runner for Go | Continous Integration library

I solved this by blowing away everything in my /vendor dir, and .gitignoring it. This forced GitHub actions to redownload everything. Not sure if this was the most efficient solution, but worked for me!

Thanks to the help I got it working:

As @rodolfo has suggested, I reproduce the solution mentioned on Github as it might help someone else.

Apparently using // #nosec G402 on the same line as the if statement fixes the problem:

The screenshots you post aren't errors, they're warnings from your IDE about potential problems in your code.

But testing.T.Errorf does not support %w (it's the same as fmt.Sprintf in what it does and doesn't accept), so the warnings are correct.

The messages do not stop your code from building and running, but in the case of an error, the formatting of the string will be off.

If you run the code, and there's an error, you'll get something like this (the part after %!w will depend on the exact error value you have).

You can use

The go command generally runs in the context of a main module and its dependencies. It finds the main module by looking for a go.mod file in the current working directory and its parent directories.

If your pre-commit is run in the root directory of the repository and there's no go.mod file there, commands will be run outside any module. So go mod tidy and go test ./... won't do anything for example.

You'll likely need to run those commands within each module. You can locate directories containing go.mod files in a shell script:

You can use matrix to achieve this. Below example would be helpful for you

This yaml file isn't indented properly. try:

In go, a common pattern is to have a function that returns two values, the first of which is the desired result, and the second of which is type error.

Typically, if an implementation cannot provide a value because of some error e, it will return nil, e or return , e.

It doesn't just have to be one such desired result value, however - sometimes there will be zero or more than one desired result values. Basic rule: if the last return value of a function is error typed, and the docs don't say otherwise, always check that last return value.

So, when you see such a pattern in a return signature - you should not discard the last result with a ignored return or an assign to '_', but should check that value to make sure it is non-nil before continuing.

The first of those anti-patterns is what the linter is warning you about. You can check the error argument thusly (I'm assuming that there are zero "desired result" values here):