Skip to content

Conversation

@sbueringer
Copy link
Member

Signed-off-by: Stefan Büringer [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Signed-off-by: Stefan Büringer [email protected]
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-area PR is missing an area label labels Aug 19, 2025
@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Aug 19, 2025
@sbueringer
Copy link
Member Author

sbueringer commented Aug 19, 2025

/hold

@JoelSpeed Looks like kubernetes-sigs/kube-api-linter#140 affected only one exclude? Is this intended? :)

EDIT: Took another look at the PR, okay seems intended. But should other linters also include the parent struct name?

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 19, 2025
@sbueringer sbueringer added the area/ci Issues or PRs related to ci label Aug 19, 2025
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/needs-area PR is missing an area label label Aug 19, 2025
@JoelSpeed
Copy link
Contributor

Looking at the excludes we have, yes, this is the extent of the change at the moment
/approve
/lgtm

The other conditions based errors come from other linters.

Though I'm not sure why we have those excludes, we could add +listType=atomic to silence the list type one without being breaking, and the other, add a reasonable max length that's beyond what we'd expect any conditions list to ever have?

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Aug 19, 2025
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 54578feb681d69a31609ff91130776a6f1c9894e

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 19, 2025
@sbueringer
Copy link
Member Author

sbueringer commented Aug 19, 2025

Though I'm not sure why we have those excludes, we could add +listType=atomic to silence the list type one without being breaking, and the other, add a reasonable max length that's beyond what we'd expect any conditions list to ever have?

Yeah, we could do that.

But I didn't mean the condition excludes specifically. I meant all excludes :)

It would be good if ~ all KAL findings would include the parent struct to allow precise excludes

@sbueringer
Copy link
Member Author

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 19, 2025
@k8s-ci-robot k8s-ci-robot merged commit 7782ab7 into kubernetes-sigs:main Aug 19, 2025
22 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.12 milestone Aug 19, 2025
@JoelSpeed
Copy link
Contributor

Ahh right, so far I've only updated the conditions linter. In the future we probably want to expand the same change to other rules too 🤔

@sbueringer
Copy link
Member Author

Ahh right, so far I've only updated the conditions linter. In the future we probably want to expand the same change to other rules too 🤔

The earlier the better. Later it breaks more excludes 😃. But for CAPI it doesn't really matter as we don't have that much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/ci Issues or PRs related to ci cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants