Skip to content

[release-4.18] USHIFT-6088: Add verified label to rebase#5415

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-5413-to-release-4.18
Sep 6, 2025
Merged

[release-4.18] USHIFT-6088: Add verified label to rebase#5415
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-5413-to-release-4.18

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #5413

/assign pacevedom

@openshift-ci-robot
Copy link

openshift-ci-robot commented Sep 5, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-6088

Details

In response to this:

This is an automated cherry-pick of #5413

/assign pacevedom

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 requested review from agullon and pmtk September 5, 2025 21:23
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 5, 2025

@openshift-cherrypick-robot: 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-sigs/prow repository. I understand the commands that are listed here.

@ggiguash
Copy link
Contributor

ggiguash commented Sep 6, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 6, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 6, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, openshift-cherrypick-robot

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 Sep 6, 2025
@ggiguash
Copy link
Contributor

ggiguash commented Sep 6, 2025

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

@openshift-ci openshift-ci bot added 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 Sep 6, 2025
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 6, 2025
@openshift-ci-robot
Copy link

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/verified by ci

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.

@ggiguash
Copy link
Contributor

ggiguash commented Sep 6, 2025

/verified bypass

@openshift-ci-robot
Copy link

@ggiguash:

Details

In response to this:

/verified bypass

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-merge-bot openshift-merge-bot bot merged commit 7ed2902 into openshift:release-4.18 Sep 6, 2025
10 checks passed
@pacevedom
Copy link
Contributor

/cherry-pick release-4.17

@openshift-cherrypick-robot
Copy link
Author

@pacevedom: new pull request created: #5416

Details

In response to this:

/cherry-pick release-4.17

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-sigs/prow repository.

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. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants