Complaining about imports on unchanged files and linking to comments

[noahdietz]

On a recent PR, golangci-lint started complaining about files that we not part of the PR, that didn't actually need a goimports run (we ran it on the entire repo with no delta), and it emitted the findings on comments in the file rather than the imports section.

Here is the offending run.

Any idea what it could be?

[shwoodard]

Here's some photo evidence and a link to support:

Of note, it is finding issues in a directory that was not touched, and, as Noah said, it's linting a comment.

[L0ntra]

I'm having the same problem with issues being found in comments.
Running goimports on the "offending" files does nothing and running golangci-lint locally does not detect any issues.

This is not an issue in 1.47.3

[maratori]

Seems like relates to #535

[noahdietz]

Seems like relates to #535

Indeed it does. I will let the maintainers decide which to de-dupe.

[SaxyPandaBear]

In order to fix this in my GitHub CI, I had to download Go 1.19 and run go1.19 fmt ./... on my repo, which performed the necessary formatting on the comment that it cared about. My project is pinned to go1.18 so 🤷