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
vsphere: remove inactive members from OWNERS #93852
vsphere: remove inactive members from OWNERS #93852
Conversation
As a part of cleaning up inactive members (who haven't been active since beginning of 2019) from OWNERS files, this commit moves abrarshivani to emeritus_approvers section.
/retest
…On Mon, Aug 10, 2020 at 5:25 PM Kubernetes Prow Robot < ***@***.***> wrote:
@nikhita <https://github.com/nikhita>: The following test *failed*, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce-100-performance 53e87dd
<53e87dd>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/93852/pull-kubernetes-e2e-gce-100-performance/1292761646808174592/> /test
pull-kubernetes-e2e-gce-100-performance
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=93852>. Your
PR dashboard. Please help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#93852 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUD2WBZSS3A6IM2NXEDR77N23ANCNFSM4PZZFGXQ>
.
|
/retest
…On Mon, Aug 10, 2020 at 5:37 PM Kubernetes Prow Robot < ***@***.***> wrote:
@nikhita <https://github.com/nikhita>: The following tests *failed*, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-kubernetes-e2e-gce-100-performance 53e87dd
<53e87dd>
link
<https://prow.k8s.io/view/gcs/kubernetes-jenkins/pr-logs/pull/93852/pull-kubernetes-e2e-gce-100-performance/1292761646808174592/> /test
pull-kubernetes-e2e-gce-100-performance
pull-kubernetes-verify 53e87dd
<53e87dd>
link
<https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/93852/pull-kubernetes-verify/1292761646820757509> /test
pull-kubernetes-verify
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=93852>. Your
PR dashboard. Please help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#93852 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUAMNDOCQZ7Z4LNTT5TR77PJ3ANCNFSM4PZZFGXQ>
.
|
/retest
…On Mon, Aug 10, 2020 at 8:07 PM Kubernetes Prow Robot < ***@***.***> wrote:
@nikhita <https://github.com/nikhita>: The following test *failed*, say
/retest to rerun all failed tests:
Test name Commit Details Rerun command
pull-kubernetes-verify 53e87dd
<53e87dd>
link
<https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/93852/pull-kubernetes-verify/1292796249862311937> /test
pull-kubernetes-verify
Full PR test history
<https://prow.k8s.io/pr-history?org=kubernetes&repo=kubernetes&pr=93852>. Your
PR dashboard. Please help us cut down on flakes by linking to
<https://git.k8s.io/community/contributors/devel/sig-testing/flaky-tests.md#filing-issues-for-flaky-tests>
an open issue
<https://github.com/kubernetes/kubernetes/issues?q=is:issue+is:open> when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
<https://git.k8s.io/community/contributors/guide/pull-requests.md>. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
<https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:>
repository. I understand the commands that are listed here
<https://go.k8s.io/bot-commands>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#93852 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUHJ7U5UVFV4NSLL35LSAAAYVANCNFSM4PZZFGXQ>
.
|
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
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: divyenpatel, nikhita 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 |
Ref: kubernetes/org#2076
As a part of cleaning up inactive members (who haven't been active since
beginning of 2019) from OWNERS files, this commit moves abrarshivani to
emeritus_approvers section.
cc @abrarshivani @mrbobbytables
/kind cleanup
/assign @divyenpatel
Does this PR introduce a user-facing change?: