-
Notifications
You must be signed in to change notification settings - Fork 40
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
Implementing Lint CI Check for Consistent Coding Practices #159
Comments
/assign |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
Totally agree on this. It would also be nice to make this approach consistent across all Go projects under the Falcosecurity org. |
Issues go stale after 90d of inactivity. Mark the issue as fresh with Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with Provide feedback via https://github.com/falcosecurity/community. /lifecycle stale |
/remove-lifecycle stale |
@leogr: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Motivation
Linting code is a fundamental practice for ensuring consistent coding standards within a project. Integrating a linting CI check into the development workflow is considered a best practice, especially as many open-source projects already adopt this approach.
Also some repositories of falco have incorporated lint CI checks falcosidekick and falcoctl.
Following same pattern, it's beneficial to set up golangci-lint as the linter for this repository as well
Feature
Alternatives
Additional context
@leogr @FedeDP Please provide your feedback I will start working on it!!
The text was updated successfully, but these errors were encountered: