Skip to content

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-16-073749_amd64-2024-07-16_arm64-2024-07-16#3644

Closed
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-16-073749_amd64-2024-07-16_arm64-2024-07-16
Closed

NO-ISSUE: rebase-release-4.15-4.15.0-0.nightly-2024-07-16-073749_amd64-2024-07-16_arm64-2024-07-16#3644
microshift-rebase-script[bot] wants to merge 4 commits intorelease-4.15from
rebase-release-4.15-4.15.0-0.nightly-2024-07-16-073749_amd64-2024-07-16_arm64-2024-07-16

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.15.0-0.nightly-2024-07-16-073749
arm64: 4.15.0-0.nightly-arm64-2024-07-16-065722
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1813423615727636480

/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 Jul 17, 2024
@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-07-16-073749
arm64: 4.15.0-0.nightly-arm64-2024-07-16-065722
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.15-rebase-on-nightlies/1813423615727636480

/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 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 Jul 17, 2024
@openshift-ci openshift-ci bot requested review from ggiguash and jogeo July 17, 2024 04:14
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2024

[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 pmtk for approval. For more information see the Kubernetes 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-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 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.

@pmtk
Copy link
Member

pmtk commented Jul 17, 2024

/close

@openshift-ci openshift-ci bot closed this Jul 17, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 17, 2024

@pmtk: Closed this PR.

Details

In response to this:

/close

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.

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