-
Notifications
You must be signed in to change notification settings - Fork 211
Conversation
/approve |
/hold |
/lgtm |
In general, I think we should strive to have more than 1 person listed in each owners file |
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.
We have a couple of OWNERS files with single approvers. Imo we should ahve at least 2 for each component.
/unhold |
cd2783b
to
65a0fdd
Compare
/retest |
* Add OWNERS file to ml-pipelines * Add owners file for pachyderm * Add ceph-nano OWNERS file * Add OWNERS file for model-mesh * Add OWNERS to odh-notebook-controller * Add OWNERS servicemesh * Add OWNERS trino * Add OWNERS to odh-dashboard * Add OWNERS to hue * Add OWNERS for jupyterhub Signed-off-by: Landon LaSmith <LLaSmith@redhat.com>
65a0fdd
to
c40e5fa
Compare
/approve Approving based on previous +1 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: accorvin, LaVLaS 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 |
/lgtm |
@LaVLaS: you cannot LGTM your own PR. 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. |
/lgtm |
Signed-off-by: Landon LaSmith LLaSmith@redhat.com
Description
Adds an OWNERS file to every component to ensure that the CI system requires PR reviews from contributors closest to the code change
Closes #646
How Has This Been Tested?
N/A
Merge criteria:
Signoff from the relevant component owners