NO-JIRA: Update OWNERS files for NI&D Areas#2052
Conversation
|
@gcs278: This pull request explicitly references no jira issue. DetailsIn 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci-robot
added
the
jira/valid-reference
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
| - melvinjoseph86 | ||
| - rhamini3 | ||
| reviewers: | ||
| - alebedev87 |
There was a problem hiding this comment.
I think we can drop Andrey from reviewers too and spare him some GitHub notifications.
Sync approvers and reviewers with the current NID team roster to match cluster-ingress-operator OWNERS. Previously, approvers were a smaller subset; this update aligns both lists.
gcs278
force-pushed
the
update-owners-nid
branch
from
946ed65 to
c623832
Compare
|
@gcs278: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
3 participants
Sync approvers and reviewers with the current NID team roster to match cluster-ingress-operator OWNERS. Previously, approvers were a smaller subset; this update aligns both lists.