Is it possible to exclude a single file in a package

[JimFawkes]

I have an autogenerated file in a go package in my project. I want to run the linters and formatters for all non autogenerated files in that go package. However I have trouble excluding the file via the exclusions section in the config.

Is this not possible or am I doing something wrong?

[ldez]

Hello,

The generated file should have a comment that follow the convention:

^// Code generated .* DO NOT EDIT\.$

https://pkg.go.dev/cmd/go#hdr-Generate_Go_files_by_processing_source

Note: in all cases, your files (generated or not) must compile https://golangci-lint.run/docs/welcome/faq/#why-is-it-not-possible-to-skipignore-typecheck-errors

[JimFawkes]

Hi Ldez,

thanks for answering and for all the work you do!

Yes the autogenerated file has a similar comment not one matching that regex exactly though.
The file contains the comment:

// DO NOT EDIT. Generated File from: some-template.tpl.
// Generated code. DO NOT EDIT.

However in my config file I have set exclusions.generated: lax which I assume/expect to exclude my generated file. I also added the path to the autogenerated file both explicitly and via a more generic regex to the exclusions.paths and tried to define a specific exclusion linter rule.

The config file contains amongst other settings this:

linters:
  exclusions:
    generated: lax
    rules:
      - linters:
          - goconst
        path: internal/path/to/my/autogenerated/file.go
   paths:
      # Skip files that are generated
      - internal/path/to/my/autogenerated/file.go

The linter that gives me trouble is goconst. Everything compiles and works it is just that I can't ignore the goconst flagged issues caused by the autogenerated file. I don't have this problem when I run goconst directly and ignore the autogenerated file. The rest of the config seems to be working as expected.

For context, this issue is appearing now after we bumped the go version from 1.25.2 to 1.26.2 and golangci-lint from 2.6.2 to 2.12.2.

[ldez]

This is a problem with the way goconst works: it accumulates the occurrences from a package and report them for only one file.

In your case, the report is on a sibling file of the generated one, so golangci-lint cannot exclude it as the report is not is the file to exclude.

Sadly, the goconst behavior cannot be controlled by golangci-lint.

For context, this issue is appearing now after we bumped the go version from 1.25.2 to 1.26.2 and golangci-lint from 2.6.2 to 2.12.2.

This is related to a new version of goconst: the behavior has been extended to new symbols.

In the next version of golangci-lint, I added an option exclude-types to restore the previous behavior.
But before the next release of golangci-lint, I don't have other solution than excluded the package instead the file.

linters:
  exclusions:
    generated: lax
    rules:
      - linters:
          - goconst
        path: internal/path/to/my/autogenerated/.+

[JimFawkes]

Ah thanks, that makes sense. I'll disable goconst then for this package until we can switch to the newest version.