-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Fix function comment to consistent with its name #70903
Conversation
Signed-off-by: PingWang <wang.ping5@zte.com.cn>
@ping035627: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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 @ping035627. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/lgtm |
/assign @yliaog |
/lgtm |
@yliaog Excuse me, can this pr be merged? Need approved label. Thanks. |
/release-note-none |
@justinsb Excuse me, can this pr be merged? Need approved label. Thanks. |
/lgtm |
@k82cn the approve label doesn't work, can you help to see what's going on? |
I'm not in approver list staging/src/k8s.io/apiserver/OWNERS :) |
@lavalamp Excuse me, can this pr be merged? Need approved label. Thanks. |
@deads2k hi, can you review this pr? Need approved label. Thanks. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: k82cn, ping035627, sttts 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 |
What type of PR is this?
/kind cleanup
**What this PR does / why we need it: **
Fix function comment to consistent with its name.
Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
release-note
NONE