Skip to content

rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14#1511

Merged
openshift-merge-robot merged 3 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14
Mar 16, 2023
Merged

rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14#1511
openshift-merge-robot merged 3 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.13.0-0.nightly-2023-03-14-053612
arm64: 4.13.0-0.nightly-arm64-2023-03-14-173645
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1636230953498054656

/label tide/merge-method-squash

@microshift-rebase-script
Copy link
Contributor Author

Extra messages:

@microshift-rebase-script microshift-rebase-script bot requested a review from pmtk March 16, 2023 05:16
@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Mar 16, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2023

@microshift-rebase-script[bot]: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14

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 requested review from dhellmann and fzdarsky March 16, 2023 05:17
@ggiguash
Copy link
Contributor

/lgtm
/label backport-risk-assessed
/label bugzilla/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. labels Mar 16, 2023
@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 16, 2023
Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Mar 16, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2023

[APPROVALNOTIFIER] This PR is APPROVED

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

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
Copy link
Contributor

openshift-ci bot commented Mar 16, 2023

@microshift-rebase-script: 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.

@openshift-merge-robot openshift-merge-robot merged commit 9b68bdc into release-4.13 Mar 16, 2023
@openshift-merge-robot openshift-merge-robot deleted the rebase-4.13.0-0.nightly-2023-03-14-053612_amd64-2023-03-14_arm64-2023-03-14 branch March 16, 2023 08:33
@copejon copejon mentioned this pull request May 2, 2023
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. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

10 participants