-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
golangci-lint should ignore node_modules #18803
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
So maybe we could run backend lint before frontend lint in CI to avoid that? |
That sounds like a workaround that will only work on CI. It needs to work locally too. Also, generally we want to run frontend/backend targets in parallel so folder absence can not be guaranteed. |
This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions. |
|
Fixed by #18708 |
Not really fixed with that, |
So is there any solution to skip node_modules? It seems that this issue is turning in circles since 2 years 😂 |
No, it needs to happen in golang first: golang/go#42965. |
CI failure seen on https://drone.gitea.io/go-gitea/gitea/51286/1/6
It seems golangi-lint tries to access files in
node_modules
which is completely unnecessary and likely a reason for its long runtime. It might be possible to pass a list of files to it via golangci/golangci-lint#301 (comment), thought I'm not sure whether that usage actually works (golangci/golangci-lint#2568).I recently added the
skip-dirs
option atgitea/.golangci.yml
Lines 27 to 30 in 1ab88da
The text was updated successfully, but these errors were encountered: