-
Notifications
You must be signed in to change notification settings - Fork 893
merge queue: embarking unstable (1a6eeb2), #7786, #7771, #7778 and #7777 together #7796
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
Conversation
…n-el-blobs-2 # Conflicts: # beacon_node/beacon_chain/src/fetch_blobs/fetch_blobs_beacon_adapter.rs # beacon_node/beacon_chain/src/metrics.rs
|
|
✨ Pull request #7778 which was ahead in the queue has been dequeued (for the following reason:
checks failed
). The pull request #7777 has been re-embarked. ✨Branch unstable (1a6eeb2), #7786, #7771, #7778 and #7777 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #7777.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
default
for merge:check-success=local-testnet-success
check-success=test-suite-success
Required conditions to stay in the queue:
#approved-reviews-by >= 1
check-success=license/cla
check-success=target-branch-check
label!=do-not-merge