-
Notifications
You must be signed in to change notification settings - Fork 276
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
Align the retryDelayMinutes deprecation notice with the standard form #3204
Align the retryDelayMinutes deprecation notice with the standard form #3204
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: tenzen-y 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 |
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/assign @mbobrovskyi |
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.
I think we missed to generate helm templates and website references.
Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
8e845c3
to
00cb8bb
Compare
Ah, that's true. Thanks. I updated this PR. |
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.
/lgtm
Thanks!
LGTM label has been added. Git tree hash: 1410b7b966426081cab50e0849225e599d791225
|
…kubernetes-sigs#3204) Signed-off-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
API deprecation notice should be aligned with standardized form so that linter can detect the deprecation comment in external projects.
https://go.dev/wiki/Deprecated
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?