Replies: 0 comments 2 replies
-
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I'm not sure why this was moved to "discussion". I consider it a bug that the default github action fails to find issues that a manual run (from inside a github action) finds... |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Welcome
Description of the problem
I have a github repo with multiple golang modules in it.
I found that running
golangci-lint run ./...
at the root will not find issues in any modules that are in sub-directories (maybe another bug?).However, changing working directory to the golang sub-module and running the above will find the issues.
Because of that, I have created a github action that runs golangci-lint each in golang module.
However, the "github action" version of golangci-lint fails to find problems, while running
golangci-lint run ./...
manually in the github action does find the problems.Here are two example runs from my public repo:
https://github.com/veqryn/slog-context/actions/runs/7069141193/job/19244513761?pr=1
https://github.com/veqryn/slog-context/actions/runs/7069162742/job/19244558387?pr=1
Version of golangci-lint
Configuration
Go environment
go 1.21.4 (inside github action)
Verbose output of running
A minimal reproducible example or link to a public repository
Validation
Beta Was this translation helpful? Give feedback.
All reactions