Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Merged
merged 2 commits into from
Nov 8, 2023

Conversation

serverless-qe
Copy link

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 Dec 10, 2022
@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

1 similar comment
@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe
Copy link
Author

OCF Webhook is merging this PR

@serverless-qe serverless-qe merged commit 9d6e057 into release-next Nov 8, 2023
5 of 6 checks passed
@dsimansk
Copy link

dsimansk commented Nov 8, 2023

Ahh, I should have put /hold on the PR. Well, it will resync again tomorrow.

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.

3 participants