Skip to content

NO-ISSUE: rebase-4.14.0-0.nightly-2023-12-05-182805_amd64-2023-12-05_arm64-2023-12-05#2690

Merged
openshift-merge-bot[bot] merged 4 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2023-12-05-182805_amd64-2023-12-05_arm64-2023-12-05
Dec 6, 2023
Merged

NO-ISSUE: rebase-4.14.0-0.nightly-2023-12-05-182805_amd64-2023-12-05_arm64-2023-12-05#2690
openshift-merge-bot[bot] merged 4 commits intorelease-4.14from
rebase-4.14.0-0.nightly-2023-12-05-182805_amd64-2023-12-05_arm64-2023-12-05

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.14.0-0.nightly-2023-12-05-182805
arm64: 4.14.0-0.nightly-arm64-2023-12-05-154636
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1732263875853684736

/label tide/merge-method-squash
/label cherry-pick-approved
/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 Dec 6, 2023
@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-2023-12-05-182805
arm64: 4.14.0-0.nightly-arm64-2023-12-05-154636
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.14-rebase-on-nightlies/1732263875853684736

/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 kubernetes/test-infra repository.

@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 Dec 6, 2023
@openshift-ci openshift-ci bot requested review from ggiguash and jogeo December 6, 2023 05:07
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 6, 2023

@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/test-infra repository. I understand the commands that are listed here.

@copejon
Copy link
Contributor

copejon commented Dec 6, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 6, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 6, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: copejon, 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 Dec 6, 2023
@openshift-merge-bot openshift-merge-bot bot merged commit 0b9707e into release-4.14 Dec 6, 2023
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-4.14.0-0.nightly-2023-12-05-182805_amd64-2023-12-05_arm64-2023-12-05 branch December 6, 2023 22:56
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