-
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
Request: Add ehashman as a sig-node API review shadow #104848
Conversation
@ehashman: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The 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. |
+1 /lgtm |
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.
/approve
@@ -487,6 +487,7 @@ aliases: | |||
- derekwaynecarr | |||
- tallclair | |||
- yujuhong | |||
- ehashman |
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.
+1 to increasing active API reviewers here
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ehashman, liggitt 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 |
@derekwaynecarr @dchen1107 as a follow-up, if some of the other folks in this alias aren't actively participating in node API reviews any more, it would be helpful to keep this list trimmed to help focus assignments/involvement to maximize knowledge transfer |
/lgtm |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
I would like to be an API review shadow for the 1.23 cycle. SIG Node identified some bandwidth problems in 1.22 on API reviews so this is potentially one way I can help.
Adding myself as a reviewer per instructions in the previous SIG Arch meeting.
/sig architecture node
/assign @derekwaynecarr @liggitt
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: