Skip to content

"NO-ISSUE: rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007" - #1339

Merged
openshift-merge-robot merged 4 commits into
release-4.12from
rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007
Feb 9, 2023
Merged

"NO-ISSUE: rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007"#1339
openshift-merge-robot merged 4 commits into
release-4.12from
rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007

Conversation

@microshift-rebase-script

Copy link
Copy Markdown
Contributor

rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007

/label tide/merge-method-squash

@openshift-ci

openshift-ci Bot commented Feb 8, 2023

Copy link
Copy Markdown
Contributor

@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.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007

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 Feb 8, 2023
@openshift-ci
openshift-ci Bot requested review from dhellmann and fzdarsky February 8, 2023 05:20
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 8, 2023
@microshift-rebase-script
microshift-rebase-script Bot force-pushed the rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007 branch from ce90f85 to e24047a Compare February 9, 2023 05:26
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Feb 9, 2023
@ggiguash

ggiguash commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

/retest

@pmtk

pmtk commented Feb 9, 2023

Copy link
Copy Markdown
Member

Testing stuff...

/retitle "NO-ISSUE: rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007"

@openshift-ci openshift-ci Bot changed the title rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007 "NO-ISSUE: rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007" Feb 9, 2023
@openshift-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

@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.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007"

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 9, 2023
@openshift-ci-robot

Copy link
Copy Markdown

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

Details

In response to this:

rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007

/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

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

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

@ggiguash

ggiguash commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

/label backport-risk-assessed
/lgtm

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 9, 2023
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 9, 2023
@openshift-ci

openshift-ci Bot commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, 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 Feb 9, 2023
@ggiguash

ggiguash commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

/label bugzilla/valid-bug

@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 Feb 9, 2023
@jogeo

jogeo commented Feb 9, 2023

Copy link
Copy Markdown
Contributor

/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 Feb 9, 2023
@openshift-merge-robot
openshift-merge-robot merged commit fb02423 into release-4.12 Feb 9, 2023
@openshift-merge-robot
openshift-merge-robot deleted the rebase-4.12.0-0.nightly+amd64-2023-02-04-034821+arm64-2023-02-07-004007 branch February 9, 2023 16:02
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.