Skip to content

NO-ISSUE: rebase-5.0.0 0-nightly-2026-07-23-224236-amd64-2026-07-23-arm64-2026-07-23#7099

Merged
openshift-merge-bot[bot] merged 12 commits into
openshift:mainfrom
pacevedom:rebase-33d8b2c538-5.0.0-0.nightly-2026-07-23-224236_amd64-2026-07-23_arm64-2026-07-23
Jul 25, 2026
Merged

NO-ISSUE: rebase-5.0.0 0-nightly-2026-07-23-224236-amd64-2026-07-23-arm64-2026-07-23#7099
openshift-merge-bot[bot] merged 12 commits into
openshift:mainfrom
pacevedom:rebase-33d8b2c538-5.0.0-0.nightly-2026-07-23-224236_amd64-2026-07-23_arm64-2026-07-23

Conversation

@pacevedom

Copy link
Copy Markdown
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

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.

@ggiguash

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 24, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@pacevedom

Copy link
Copy Markdown
Contributor Author

/retest

@copejon

copejon commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

/verified by ci
/lgtm

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@copejon: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci
/lgtm

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 openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2026
@copejon

copejon commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci

openshift-ci Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, ggiguash, pacevedom

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [copejon,ggiguash,pacevedom]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@pacevedom

Copy link
Copy Markdown
Contributor Author

/test test-rebase

@pacevedom

Copy link
Copy Markdown
Contributor Author

/retest

2 similar comments
@pacevedom

Copy link
Copy Markdown
Contributor Author

/retest

@pacevedom

Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci

openshift-ci Bot commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

@pacevedom: all tests passed!

Full PR test history. Your PR dashboard.

Details

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-merge-bot
openshift-merge-bot Bot merged commit 07ebd95 into openshift:main Jul 25, 2026
16 checks passed
@pacevedom
pacevedom deleted the rebase-33d8b2c538-5.0.0-0.nightly-2026-07-23-224236_amd64-2026-07-23_arm64-2026-07-23 branch July 25, 2026 09:46
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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants