Skip to content

USHIFT-5925: Cert manager auto rebase#5355

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
eslutsky:cert-manager-rebase
Sep 26, 2025
Merged

USHIFT-5925: Cert manager auto rebase#5355
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
eslutsky:cert-manager-rebase

Conversation

@eslutsky
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 Aug 21, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 21, 2025

@eslutsky: This pull request references USHIFT-5925 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 story to target the "4.20.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.

@openshift-ci openshift-ci bot requested review from dhensel-rh and pacevedom August 21, 2025 14:51
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 21, 2025
@eslutsky eslutsky force-pushed the cert-manager-rebase branch 5 times, most recently from 3aaab58 to 7c1d3a2 Compare August 26, 2025 17:14
@eslutsky eslutsky force-pushed the cert-manager-rebase branch from 257ed68 to 6be1f2b Compare September 5, 2025 14:23
@eslutsky eslutsky force-pushed the cert-manager-rebase branch 2 times, most recently from 72c83d2 to fa74b4f Compare September 17, 2025 20:32
Signed-off-by: Evgeny Slutsky <eslutsky@redhat.com>
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.

/lgtm

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

openshift-ci bot commented Sep 25, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

@eslutsky
Copy link
Contributor Author

/test e2e-aws-tests-bootc-arm

1 similar comment
@pacevedom
Copy link
Contributor

/test e2e-aws-tests-bootc-arm

@eslutsky
Copy link
Contributor Author

/verified by release-ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 26, 2025
@openshift-ci-robot
Copy link

@eslutsky: This PR has been marked as verified by release-ci.

Details

In response to this:

/verified by release-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.

@openshift-merge-bot openshift-merge-bot bot merged commit 62c94a1 into openshift:main Sep 26, 2025
11 of 12 checks passed
@eslutsky
Copy link
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@eslutsky: new pull request created: #5538

Details

In response to this:

/cherry-pick release-4.20

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.

eslutsky added a commit to eslutsky/microshift that referenced this pull request Oct 7, 2025
…rebase"

This reverts commit 62c94a1, reversing
changes made to 10c44e7.
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. 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