Skip to content

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-05-18-194638_amd64-2026-05-18_arm64-2026-05-18#6691

Merged
openshift-merge-bot[bot] merged 5 commits into
mainfrom
rebase-release-5.0-5.0.0-0.nightly-2026-05-18-194638_amd64-2026-05-18_arm64-2026-05-18
May 19, 2026
Merged

NO-ISSUE: rebase-release-5.0-5.0.0-0.nightly-2026-05-18-194638_amd64-2026-05-18_arm64-2026-05-18#6691
openshift-merge-bot[bot] merged 5 commits into
mainfrom
rebase-release-5.0-5.0.0-0.nightly-2026-05-18-194638_amd64-2026-05-18_arm64-2026-05-18

Conversation

@microshift-rebase-script
Copy link
Copy Markdown
Contributor

@microshift-rebase-script microshift-rebase-script Bot commented May 19, 2026

amd64: 5.0.0-0.nightly-2026-05-18-194638
arm64: 5.0.0-0.nightly-arm64-2026-05-18-185007
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-5.0-periodics-rebase-on-nightlies/2056585847460859904

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 19, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 19, 2026

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

amd64: 5.0.0-0.nightly-2026-05-18-194638
arm64: 5.0.0-0.nightly-arm64-2026-05-18-185007
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-5.0-periodics-rebase-on-nightlies/2056585847460859904

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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 tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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 May 19, 2026
@openshift-ci openshift-ci Bot requested review from jogeo and vanhalenar May 19, 2026 04:22
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: microshift-rebase-script[bot]
Once this PR has been reviewed and has the lgtm label, please assign copejon for approval. For more information see the Code Review Process.

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

Details 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-bot
Copy link
Copy Markdown
Contributor

/retest-required

Remaining retests: 0 against base HEAD 8848cdd and 2 for PR HEAD 27662dc in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 19, 2026

@microshift-rebase-script[bot]: 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 c52d541 into main May 19, 2026
16 checks passed
@openshift-merge-bot openshift-merge-bot Bot deleted the rebase-release-5.0-5.0.0-0.nightly-2026-05-18-194638_amd64-2026-05-18_arm64-2026-05-18 branch May 19, 2026 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant