-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add linting based on the elastic-agent-libs for Beats #30545
Comments
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Just to avoid future problems, this configuration simply does not work. I tested it manually and had to use
|
I assigned this to you @rdner, if you run out of time for it feel free to send it back to me. |
I think it stalled due to other priorities, I don't think @rdner is actively working on this. It's not critical to do in 8.2. We can unassign it change the label if we want and someone can take it once they have time for it. |
Perfect, assigned back to you then |
Now that a base configuration for golangci-lint has been created and setup for elastic-agent-libs we should do the same for the beats repository.
See #30150 for the related PRs.
Since the beats repository is so large we will need to be more careful when rolling it out to ensure the new linters do not slow down the development workflow.
We will likely also only want to have the linter only prevent new issues initially, rather than fixing all existing issues. PRs to address existing issues can be quite large, for example #30483.
See go-libaudit for an example of how to configure the linter to only find new issues: https://github.com/elastic/go-libaudit/blob/227948a588b4c181d09a55154a476372525be193/.github/workflows/golangci-lint.yml#L29-L30
The text was updated successfully, but these errors were encountered: