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
gh: workflows: clarify reference to issue #23283 #31118
gh: workflows: clarify reference to issue #23283 #31118
Conversation
/test |
@julianwiedmann FYI that since this is being opened from a fork I'm not sure if this is being tested with your changes or not. |
Could you like to the PR which has resolved this? Because last time I checked, the underlying issue wasn't actually fixed in Cilium, it was only "resolved" by adjusting the See also my comment here: #23283 (comment) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(as per comment above)
Clarify that while the issue was closed as resolved, this actually only applies to scenarios where the kind.sh script is used. Signed-off-by: Julian Wiedmann <jwi@isovalent.com>
7529c2d
to
745c49f
Compare
Thanks! Marco pointed out the same to me earlier, we came to the conclusion that it's probably best to point right at your :amaze: comment and not the high-level issue. Updated the PR. |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Clarify that while the issue was closed as resolved, this actually only
applies to scenarios where the kind.sh script is used.