Skip to content

NO-ISSUE: Update DOWNSTREAM owners files #973

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
Merged
merged 1 commit into from
Mar 14, 2025
Merged

NO-ISSUE: Update DOWNSTREAM owners files #973

merged 1 commit into from
Mar 14, 2025

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Mar 6, 2025

No description provided.

@openshift-ci openshift-ci bot requested review from grokspawn and oceanc80 March 6, 2025 14:53
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. labels Mar 6, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Mar 6, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 6, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grokspawn, tmshort

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

@tmshort tmshort changed the title Update DOWNSTREAM owners files NO-ISSUE: Update DOWNSTREAM owners files Mar 6, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 6, 2025
@openshift-ci-robot
Copy link

@tmshort: This pull request explicitly references no jira issue.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

11 similar comments
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 6dd1017 and 2 for PR HEAD e5f3b5d in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 601c4fb and 1 for PR HEAD e5f3b5d in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Mar 14, 2025 •
edited
Loading

@tmshort: The following tests 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/okd-scos-e2e-aws-ovn e5f3b5d link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-olm-flaky e5f3b5d 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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 601c4fb and 2 for PR HEAD e5f3b5d in total

@openshift-merge-bot openshift-merge-bot bot merged commit 549f760 into openshift:main Mar 14, 2025
13 of 15 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.19.0-202503141147.p0.g549f760.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.19.0-202503141147.p0.g549f760.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.19.0-202503141147.p0.g549f760.assembly.stream.el9.
All builds following this will include this PR.

@tmshort tmshort deleted the owners branch May 16, 2025 14:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@grokspawn grokspawn grokspawn approved these changes

@oceanc80 oceanc80 Awaiting requested review from oceanc80

Assignees

@grokspawn grokspawn

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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.
4 participants
@tmshort @openshift-ci-robot @openshift-bot @grokspawn