Implementing Lint CI Check for Consistent Coding Practices

[GLVSKiriti]

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!!

[GLVSKiriti]

/assign

[poiana]

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

[leogr]

/remove-lifecycle stale

[leogr]

Totally agree on this. It would also be nice to make this approach consistent across all Go projects under the Falcosecurity org.