Skip to content

Comments

🤖 triggering CI on branch 'release-next' after synching from upstream/main#121

Merged
openshift-merge-bot[bot] merged 1 commit intorelease-nextfrom
release-next-ci
May 9, 2025
Merged

🤖 triggering CI on branch 'release-next' after synching from upstream/main#121
openshift-merge-bot[bot] merged 1 commit intorelease-nextfrom
release-next-ci

Conversation

@serverless-qe
Copy link
Collaborator

No description provided.

@openshift-ci
Copy link

openshift-ci bot commented May 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: serverless-qe

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

1 similar comment
@openshift-ci
Copy link

openshift-ci bot commented May 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: serverless-qe

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-merge-bot openshift-merge-bot bot merged commit 6a955d4 into release-next May 9, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant