Skip to content

merge queue: checking #238 on main (1c686d3) - #239

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/4df7dcbdaa
Closed

mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/4df7dcbdaa

Conversation

@mergify

@mergify mergify Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch grateful-hachis-xi9vzd of the default queue, to test #238 before it merges into main. Pushing to this branch or closing this pull request removes #238 from the queue.

What this draft tests

Mergify checks that #238 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at 1c686d3
  2. #238, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #238 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 1c686d3c6cfcbeb34fa2e5de2fa7b5e1f88c46c7
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 238
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge

No extra conditions.

Required conditions to stay in the queue

None

@mergify mergify Bot closed this Oct 21, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/4df7dcbdaa branch October 21, 2026 11:39
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.

0 participants