Skip to content

Conversation

@mergify
Copy link

@mergify mergify bot commented Jan 16, 2026

✨ Pull request #8666 which was ahead in the queue has been dequeued (for the following reason: checks failed). The pull request [#8665 + #8666] has been re-embarked. ✨

Branch unstable (acc746d) and [#8665 + #8666] are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of [#8665 + #8666].
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:

---
checking_base_sha: acc746d9470c58bf525259ebfdbab82aa2dd811a
previous_failed_batches: []
pull_requests:
  - number: 8665
  - number: 8666
...

@cla-assistant
Copy link

cla-assistant bot commented Jan 16, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ macladson
❌ mergify[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

1 similar comment
@cla-assistant
Copy link

cla-assistant bot commented Jan 16, 2026

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ macladson
❌ mergify[bot]
You have signed the CLA already but the status is still pending? Let us recheck it.

@mergify mergify bot closed this Jan 16, 2026
@mergify mergify bot deleted the mergify/merge-queue/2a4d63c043 branch January 16, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants