Super-linter: Invoking golangci-lint run on individual files breaks linters in packages.

[RussellRollins]

Describe the bug
When golangci-lint is invoked against a single file, as it is here:

https://github.com/github/super-linter/blob/1e08ff6363cb45c5714b1c30039d896972287173/lib/linter.sh#L1939

This fails to properly lint a package if types are defined in another file.

To Reproduce
Steps to reproduce the behavior:

1. Create two Go files, main.go and foo.go.
2. Define Foo in foo.go.
3. Run golangci-lint run in that package, it lints fine.
4. Run the super-linter against that package, it fails to lint with: ERROR:[level=warning msg="[runner] Can't run linter unused: buildssa: analysis skipped: errors in package: [/github/workspace/main.go:8:8: undeclared name: Foo]"

See an example run here: https://github.com/RussellRollins/super-lint-error/runs/785695971

Expected behavior
This passes linting without failures.

Screenshots

Additional context
I can see how the current solution is used to enable the "lint only changed files" feature, but this will fall down for relatively simple Go setups.

[bznein]

We encountered the same issue and this makes SuperLinter with Golang basically unusable.
An option to run the linter on whole directories when VALIDATE_ALL_CODEBASE is True would be extremely helpful

[bznein]

Hi @RussellRollins, I created a PR #370 which aims at fixing this issue. The owners of the repo want to gather some more feedback from other GO developer. If you have some time to spare can you have a look at it and leave your opinion there? Thanks!

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[iggy]

Slow your roll bot. This is still valid.

Sorry for the noise. Trying to keep this from getting closed.

[pwmcintyre]

still valid; super-linter is totally broken for golang :(

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[jtbonhomme]

Still valid!

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[WendelHime]

still valid

[GaboFDC]

Related to #888

[karolistamutis]

What would be the workaround besides disabling Super-Linter completely for go? Having the same issue.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[masih]

Not stale

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[WendelHime]

not stale

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed in 14 days if no further activity occurs.
Thank you for your contributions.

If you think this issue should stay open, please remove the O: stale 🤖 label or comment on the issue.

[bznein]

not stale