Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-06-11-200645_amd64-2024-06-11_arm64-2024-06-12#3479

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-06-11-200645_amd64-2024-06-11_arm64-2024-06-12
Jun 13, 2024
Merged

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-06-11-200645_amd64-2024-06-11_arm64-2024-06-12#3479
openshift-merge-bot[bot] merged 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-06-11-200645_amd64-2024-06-11_arm64-2024-06-12

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-06-11-200645
arm64: 4.15.0-0.nightly-arm64-2024-06-12-223752
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1801102588519649280

/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.15.0-0.nightly-2024-06-11-200645
arm64: 4.15.0-0.nightly-arm64-2024-06-12-223752
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1801102588519649280

/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 Jun 13, 2024
@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 Jun 13, 2024
@openshift-ci openshift-ci bot requested review from pliurh and pmtk June 13, 2024 04:14
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

@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 Jun 13, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 13, 2024

[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 Jun 13, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f12df98 into release-4.15 Jun 13, 2024
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-release-4.15-4.15.0-0.nightly-2024-06-11-200645_amd64-2024-06-11_arm64-2024-06-12 branch June 13, 2024 13:01
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