Skip to content

NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14#1671

Merged
openshift-merge-robot merged 9 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14
Apr 14, 2023
Merged

NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14#1671
openshift-merge-robot merged 9 commits intorelease-4.13from
rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.13.0-0.nightly-2023-04-13-171034
arm64: 4.13.0-0.nightly-arm64-2023-04-14-004314
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1646740208294563840

/label tide/merge-method-squash

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 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-04-13-171034_amd64-2023-04-13_arm64-2023-04-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 added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Apr 14, 2023
@openshift-ci openshift-ci bot requested review from sallyom and zshi-redhat April 14, 2023 05:15
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 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.

@pacevedom
Copy link
Contributor

/retitle NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14

@openshift-ci openshift-ci bot changed the title rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14 NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14 Apr 14, 2023
@pacevedom
Copy link
Contributor

/label bugzilla/valid-bug
/lgtm
/label approved
/label cherry-pick-approved
/label backport-risk-assessed

@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 14, 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.13.0-0.nightly-2023-04-13-171034
arm64: 4.13.0-0.nightly-arm64-2023-04-14-004314
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.13-rebase-on-nightlies/1646740208294563840

/label tide/merge-method-squash

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

openshift-ci bot commented Apr 14, 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:

NO-ISSUE:rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-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 added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Apr 14, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 2023

@pacevedom: Can not set label approved: Must be member in one of these teams: [openshift-release-oversight]

Details

In response to this:

/label bugzilla/valid-bug
/lgtm
/label approved
/label cherry-pick-approved
/label backport-risk-assessed

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 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. labels Apr 14, 2023
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 14, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 14, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 14, 2023
@openshift-merge-robot openshift-merge-robot merged commit 7af02e3 into release-4.13 Apr 14, 2023
@openshift-merge-robot openshift-merge-robot deleted the rebase-4.13.0-0.nightly-2023-04-13-171034_amd64-2023-04-13_arm64-2023-04-14 branch April 14, 2023 06:24
@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. 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.

10 participants