-
Notifications
You must be signed in to change notification settings - Fork 295
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
🌱 OWNERS: Refresh of owners as per meeting of 2023/06/22 #2082
🌱 OWNERS: Refresh of owners as per meeting of 2023/06/22 #2082
Conversation
/lgtm |
Signed-off-by: Naadir Jeewa <[email protected]>
feed3ea
to
d022b5b
Compare
/hold |
/lgtm |
/lgtm 🙂 |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: srm09 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 |
/unhold |
/cherry-pick release-1.7 |
/cherry-pick release-1.6 |
/cherry-pick release-1.5 |
@sbueringer: new pull request could not be created: failed to create pull request against kubernetes-sigs/cluster-api-provider-vsphere#release-1.7 from head k8s-infra-cherrypick-robot:cherry-pick-2082-to-release-1.7: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","field":"head","code":"invalid"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} In response to this:
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. |
@sbueringer: new pull request could not be created: failed to create pull request against kubernetes-sigs/cluster-api-provider-vsphere#release-1.6 from head k8s-infra-cherrypick-robot:cherry-pick-2082-to-release-1.6: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"missing_field","field":"head_sha"},{"resource":"PullRequest","code":"missing_field","field":"base_sha"},{"resource":"PullRequest","code":"custom","message":"No commits between kubernetes-sigs:release-1.6 and k8s-infra-cherrypick-robot:cherry-pick-2082-to-release-1.6"}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} In response to this:
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. |
@sbueringer: new pull request created: #2128 In response to this:
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. |
/cherry-pick release-1.7 |
@sbueringer: new pull request created: #2129 In response to this:
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. |
/cherry-pick release-1.6 |
@sbueringer: new pull request created: #2130 In response to this:
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. |
What this PR does / why we need it:
Refresh of OWNERS to reflect current folk as per the meeting of 2023/06/22
Related PRs:
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 #
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note: