Skip to content

USHIFT-3122: auto-rebase update csi-snapshot-webhook and router manifests#3302

Merged
openshift-merge-bot[bot] merged 11 commits intoopenshift:mainfrom
pacevedom:rebase-70d94bd32-4.16.0-0.nightly-2024-04-29-154406_amd64-2024-04-29_arm64-2024-04-29
Apr 30, 2024
Merged

USHIFT-3122: auto-rebase update csi-snapshot-webhook and router manifests#3302
openshift-merge-bot[bot] merged 11 commits intoopenshift:mainfrom
pacevedom:rebase-70d94bd32-4.16.0-0.nightly-2024-04-29-154406_amd64-2024-04-29_arm64-2024-04-29

Conversation

@pacevedom
Copy link
Contributor

Which issue(s) this PR addresses:

Closes #

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

@pacevedom: This pull request explicitly references no jira issue.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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.

@pacevedom
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 30, 2024
@openshift-ci openshift-ci bot requested review from dhellmann and pliurh April 30, 2024 12:18
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2024
@pacevedom
Copy link
Contributor Author

/cc @copejon @ggiguash @eslutsky

@openshift-ci openshift-ci bot requested review from copejon, eslutsky and ggiguash April 30, 2024 12:20
@pacevedom
Copy link
Contributor Author

pacevedom commented Apr 30, 2024

/retitle USHIFT-3122: auto-rebase update SCCs, csi-snapshot-webhook and router manifests

@openshift-ci openshift-ci bot changed the title NO-ISSUE: auto-rebase update SCCs, csi-snapshot-webhook and router manifests USHIFT-3122: auto-rebase update SCCs, csi-snapshot-webhook and router manifests Apr 30, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Apr 30, 2024

@pacevedom: This pull request references USHIFT-3122 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses:

Closes #

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.

@pacevedom
Copy link
Contributor Author

/test microshift-metal-tests

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

@pacevedom: 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 Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 30, 2024
@pacevedom pacevedom changed the title USHIFT-3122: auto-rebase update SCCs, csi-snapshot-webhook and router manifests USHIFT-3122: auto-rebase update csi-snapshot-webhook and router manifests Apr 30, 2024
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 30, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants