Skip to content

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #122

/assign andreasgerstmayr

/cherrypick release-0.4

Signed-off-by: Andreas Gerstmayr <agerstmayr@redhat.com>
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 20, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: TRACING-5408

In response to this:

This is an automated cherry-pick of #122

/assign andreasgerstmayr

/cherrypick release-0.4

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.

@IshwarKanse
Copy link
Member

/override ci/prow/upstream-amd64-aws-e2e

Copy link

openshift-ci bot commented May 20, 2025

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e

In response to this:

/override ci/prow/upstream-amd64-aws-e2e

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.

@andreasgerstmayr
Copy link
Contributor

/lgtm

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

openshift-ci bot commented May 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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 May 20, 2025
@andreasgerstmayr
Copy link
Contributor

/label qe-approved
this branch is 100% identical with main branch

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label May 20, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented May 20, 2025

@openshift-cherrypick-robot: This pull request references TRACING-5408 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #122

/assign andreasgerstmayr

/cherrypick release-0.4

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.

@andreasgerstmayr
Copy link
Contributor

/label ux-approved
minimal ux change

@openshift-ci openshift-ci bot added the ux-approved Signifies that UX has signed off on this PR label May 20, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 246f1e6 into openshift:release-1.0 May 20, 2025
5 checks passed
@openshift-cherrypick-robot
Copy link
Author

@openshift-cherrypick-robot: new pull request created: #125

In response to this:

This is an automated cherry-pick of #122

/assign andreasgerstmayr

/cherrypick release-0.4

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. 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. qe-approved Signifies that QE has signed off on this PR ux-approved Signifies that UX has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants