Skip to content
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

Update openshift-kni mirroring OWNERS #60466

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lack
Copy link
Member

@lack lack commented Jan 9, 2025

Signed-off-by: Jim Ramsay jramsay@redhat.com

Signed-off-by: Jim Ramsay <jramsay@redhat.com>
Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lack

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 9, 2025
@openshift-ci openshift-ci bot requested review from fedepaol and slintes January 9, 2025 07:42
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@lack: no rehearsable tests are affected by this change

Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

@lack: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

- nishant-parekh
- jc-rh
- browsell
- donpenney
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These would be needed under reviewers list as well, I think?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought approver implied reviewer, but I think you're right that we should all be in both places.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The wording there seems a little ambiguous to me. An approver giving a lgtm implies an approve, but does that imply an approver is able to give a lgtm? I know in repos where I'm both reviewer and approver, I can give an lgtm without it also adding an approve, so it's not clear to me. Could be something to experiment with

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. rehearsals-ack Signifies that rehearsal jobs have been acknowledged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants