-
Notifications
You must be signed in to change notification settings - Fork 601
Enable additional linters #2414
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
@sedefsavas: 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/test-infra repository. |
@sedefsavas: The provided milestone is not valid for this repository. Milestones in this repository: [ Use 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/test-infra repository. |
Hi @sedefsavas I can help with this. Any specific linters that you want to enable? |
There are couple of PRs open in cluster-api. We can keep an eye on those: kubernetes-sigs/cluster-api#4622 and enable same ones. Some relevant ones: /assign @Evalle |
Just fyi. I try to keep an up-to-date list here: kubernetes-sigs/cluster-api#4622 for further inspiration. In general it might also make sense to compare the currently active linters in CAPI vs CAPA. |
I created a new issue for enabling comment enforcement linter, as it will be big change. |
Core cluster-api repo is enabling some additional linters, it'd be good for consistency to enable same linters.
kubernetes-sigs/cluster-api#4622
/help
/good-first-issue
/milestone 0.7.x
The text was updated successfully, but these errors were encountered: