-
Notifications
You must be signed in to change notification settings - Fork 75
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
Enhance linting to cover yaml files #1497
Comments
/good-first-issue |
@Prajyot-Parab: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. 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. |
/assign @yuanning6 I'd love to help fix this issue! Can I get some guide about where to start? |
@yuanning6 You can start by checking the other linters we have - https://github.com/kubernetes-sigs/cluster-api-provider-ibmcloud/blob/main/.golangci.yml can run we want to do same thing for yaml files to avoid issues such as 7cd7fcc |
@Prajyot-Parab Thank you so much for your guidance! I found yamllint is a popular tool to lint yaml files, can I start with this? And should I make the lint rules very strict or kind of loose? |
Yes you can start with whatever is the relevant tool, lets start with loose rules and we will make them stricter going ahead as and when required. |
@Prajyot-Parab Sure! I did some implementations and made a PR #1521, it's just for you to have an overview and see if I'm on the right direction. Please let me know any changes I should make! |
I will take a look at this today, thanks! |
Thank you! :)) |
/kind bug
/area provider/ibmcloud
What steps did you take and what happened:
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: