Skip to content

NO-ISSUE: rebase-4.14.0-0.nightly-2025-03-06-104841_amd64-2025-03-06_arm64-2025-03-08#4649

Merged
openshift-merge-bot[bot] merged 3 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2025-03-06-104841_amd64-2025-03-06_arm64-2025-03-08
Mar 10, 2025
Merged

NO-ISSUE: rebase-4.14.0-0.nightly-2025-03-06-104841_amd64-2025-03-06_arm64-2025-03-08#4649
openshift-merge-bot[bot] merged 3 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2025-03-06-104841_amd64-2025-03-06_arm64-2025-03-08

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.14.0-0.nightly-2025-03-06-104841
arm64: 4.14.0-0.nightly-arm64-2025-03-08-102130
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1898947223543091200

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

@openshift-ci-robot
Copy link

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

Details

In response to this:

amd64: 4.14.0-0.nightly-2025-03-06-104841
arm64: 4.14.0-0.nightly-arm64-2025-03-08-102130
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1898947223543091200

/label tide/merge-method-squash
/label cherry-pick-approved
/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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 10, 2025
@openshift-ci openshift-ci bot added tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. 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 Mar 10, 2025
@openshift-ci openshift-ci bot requested review from copejon and pacevedom March 10, 2025 04:55
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 10, 2025

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

@eslutsky
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Mar 10, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eslutsky, microshift-rebase-script[bot]

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:

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 Mar 10, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 32e636f into release-4.14 Mar 10, 2025
7 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-4.14.0-0.nightly-2025-03-06-104841_amd64-2025-03-06_arm64-2025-03-08 branch March 10, 2025 10:39
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. 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. 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. 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.

2 participants