Skip to content

🤖 Synchronize branch release-next to upstream/main#315

Merged
serverless-qe merged 1 commit intorelease-nextfrom
ci/release-next
Nov 20, 2023
Merged

🤖 Synchronize branch release-next to upstream/main#315
serverless-qe merged 1 commit intorelease-nextfrom
ci/release-next

Conversation

@serverless-qe
Copy link
Copy Markdown

This automated PR is to make sure the forked project's release-next branch (forked upstream's main branch) passes a CI.

@serverless-qe serverless-qe added the kind/sync-fork-to-upstream Tag used for PRs that are automatically created to merge upstream changes label Nov 20, 2023
@openshift-ci
Copy link
Copy Markdown

openshift-ci bot commented Nov 20, 2023

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: serverless-qe
Once this PR has been reviewed and has the lgtm label, please assign alanfx for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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

@serverless-qe
Copy link
Copy Markdown
Author

OCF Webhook is merging this PR

@serverless-qe serverless-qe merged commit f18f932 into release-next Nov 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/sync-fork-to-upstream Tag used for PRs that are automatically created to merge upstream changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant