Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-04-03-065948_amd64-2024-04-03_arm64-2024-04-03 #3214

Merged
merged 4 commits into from
Apr 4, 2024
Merged

NO-ISSUE: rebase-main-4.16.0-0.nightly-2024-04-03-065948_amd64-2024-04-03_arm64-2024-04-03 #3214

merged 4 commits into from
Apr 4, 2024

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.16.0-0.nightly-2024-04-03-065948
arm64: 4.16.0-0.nightly-arm64-2024-04-03-065949
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1775750374745968640

  • machine-config-operator embedded-component 1d5df20e0c3a50de5372a8dcd64769a13f773174 to a4fbf4d0991878d0f98efdc1d2bf22b877acc9ad
    • 69187002 2024-04-02T09:44:46-04:00 fix: resources were in the wrong indentation level

/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 Apr 4, 2024
@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.16.0-0.nightly-2024-04-03-065948
arm64: 4.16.0-0.nightly-arm64-2024-04-03-065949
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1775750374745968640

  • machine-config-operator embedded-component 1d5df20e0c3a50de5372a8dcd64769a13f773174 to a4fbf4d0991878d0f98efdc1d2bf22b877acc9ad
  • 69187002 2024-04-02T09:44:46-04:00 fix: resources were in the wrong indentation level

/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 Apr 4, 2024
@openshift-ci openshift-ci bot requested review from jerpeter1 and pliurh April 4, 2024 05:12
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 4, 2024

@microshift-rebase-script[bot]: all tests passed!

Full PR test history. Your PR dashboard.

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.

@pmtk
Copy link
Member

pmtk commented Apr 4, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 4, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 4, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

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 Apr 4, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 18cdbf0 into main Apr 4, 2024
9 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.16.0-0.nightly-2024-04-03-065948_amd64-2024-04-03_arm64-2024-04-03 branch April 4, 2024 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jerpeter1 jerpeter1 Awaiting requested review from jerpeter1

@pliurh pliurh Awaiting requested review from pliurh

Assignees

@pmtk pmtk

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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@openshift-ci-robot @pmtk