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.

Sign up for GitHub

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

Jump to bottom

[release-4.11] [4.13] Introduce DOWNSTREAM_OWNERS file #542

Merged
merged 1 commit into from Aug 15, 2023
Merged

[release-4.11] [4.13] Introduce DOWNSTREAM_OWNERS file #542

merged 1 commit into from Aug 15, 2023

Conversation

openshift-cherrypick-robot
Copy link

This is an automated cherry-pick of #538

/assign awgreene

@awgreene
Introduce DOWNSTREAM_OWNERS file
ce80891 
The openshift distribution of Operator Lifecycle Manager (OLM) was recently
updated to include a DOWNSTREAM_OWNERS file that specifies who has LGTM
and approval permissions. This file is expected in all OLM release
branches otherwise we won't be able to approve or LGTM pull requests to
the branches.

Signed-off-by: Alexander Greene <greene.al1991@gmail.com>
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Aug 15, 2023
Merged
@perdasilva
Copy link
Contributor

/retest

@perdasilva
Copy link
Contributor

/override approved

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2023

@perdasilva: perdasilva unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight.

In response to this:

/override approved

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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2023

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-olm-flaky ce80891 link false /test e2e-gcp-olm-flaky

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

@joelanford joelanford added 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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 15, 2023
@joelanford
Copy link
Member

Manually adding labels to force merge. This is a required change to the prow configuration, which requires the same OWNERS file name to be used in all managed branches.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 15, 2023

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-cherrypick-robot

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-merge-robot openshift-merge-robot merged commit f80ea56 into openshift:release-4.11 Aug 15, 2023
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@bandrade bandrade

@awgreene awgreene

@jianzhangbjz jianzhangbjz

@emmajiafan emmajiafan

@kuiwang02 kuiwang02

@Xia-Zhao-rh Xia-Zhao-rh

@KeenonLee KeenonLee

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet