Skip to content
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

Increase number of enabled golangci-lint linters #2072

Open
tuminoid opened this issue Nov 21, 2024 · 2 comments
Open

Increase number of enabled golangci-lint linters #2072

tuminoid opened this issue Nov 21, 2024 · 2 comments
Labels
kind/ci Categorizes issue or PR as related to CI or testing. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

BMO has 40+ linters enabled in our config whitelist. Golangci-lint has 100+ linters. Enable more linters to increase coverage and code quality.

/kind ci

@metal3-io-bot metal3-io-bot added kind/ci Categorizes issue or PR as related to CI or testing. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Nov 21, 2024
@Rozzii
Copy link
Member

Rozzii commented Dec 4, 2024

Let's propose new linters under a github discussion.
/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels Dec 4, 2024
@metal3-io-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues will close after an additional 30d of inactivity.

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

/lifecycle stale

@metal3-io-bot metal3-io-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/ci Categorizes issue or PR as related to CI or testing. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants