Skip to content

Conversation

@wangke19
Copy link
Contributor

In the current OWNERS list, some people have left RedHat and lack of reviewers and approvers.

@openshift-ci openshift-ci bot requested review from deads2k and jsafrane September 19, 2025 05:05
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2025

@wangke19: 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.

Copy link
Member

@bertinatto bertinatto left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bertinatto, wangke19

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 Sep 19, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 7fa221c into openshift:master Sep 19, 2025
4 checks passed
@wangke19 wangke19 deleted the update-owners branch September 22, 2025 04:08
@wangke19
Copy link
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@wangke19: new pull request created: #2016

In response to this:

/cherry-pick release-4.20

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.

@wangke19
Copy link
Contributor Author

/cherry-pick release-4.19

@wangke19
Copy link
Contributor Author

/cherry-pick release-4.18

@wangke19
Copy link
Contributor Author

/cherry-pick release-4.17

@wangke19
Copy link
Contributor Author

/cherry-pick release-4.16

@openshift-cherrypick-robot

@wangke19: new pull request created: #2017

In response to this:

/cherry-pick release-4.19

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.

@openshift-cherrypick-robot

@wangke19: new pull request created: #2018

In response to this:

/cherry-pick release-4.18

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.

@openshift-cherrypick-robot

@wangke19: #2015 failed to apply on top of branch "release-4.17":

Applying: Updated OWNERS
Using index info to reconstruct a base tree...
M	pkg/operator/OWNERS
Falling back to patching base and 3-way merge...
Auto-merging pkg/operator/OWNERS
CONFLICT (content): Merge conflict in pkg/operator/OWNERS
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Updated OWNERS

In response to this:

/cherry-pick release-4.17

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.

@openshift-cherrypick-robot

@wangke19: #2015 failed to apply on top of branch "release-4.16":

Applying: Updated OWNERS
Using index info to reconstruct a base tree...
M	pkg/operator/OWNERS
Falling back to patching base and 3-way merge...
Auto-merging pkg/operator/OWNERS
CONFLICT (content): Merge conflict in pkg/operator/OWNERS
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Updated OWNERS

In response to this:

/cherry-pick release-4.16

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.

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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants