Skip to content

🤖 Triggering CI on branch 'release-next' after synching to upstream/main - #1879

Open
serverless-qe wants to merge 1 commit into
release-nextfrom
release-next-ci
Open

🤖 Triggering CI on branch 'release-next' after synching to upstream/main#1879
serverless-qe wants to merge 1 commit into
release-nextfrom
release-next-ci

Conversation

@serverless-qe

Copy link
Copy Markdown
Collaborator

No description provided.

@openshift-merge-bot

Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 5fe9f20 and 2 for PR HEAD 67a0197 in total

@openshift-ci

openshift-ci Bot commented May 1, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@openshift-ci openshift-ci Bot removed the lgtm label May 1, 2026
@openshift-ci

openshift-ci Bot commented Jul 30, 2026

Copy link
Copy Markdown

[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

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