merge queue: checking #298 on main (f38b128)

[mergify]

Note

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

What this draft tests

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

1. main at f38b128
2. #298, the pull request of this batch

⏳ Where it stands: being checked

CI is running on this draft.

Waiting for

• check-success = build

Follow the default queue in the dashboard

What happens next

• Once the checks pass and every merge condition is met, Mergify merges #298 into main and closes this draft.
• If a check fails, Mergify removes #298 from the queue and closes this draft.

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: f38b128e17c4cf654f8753dc880c11cba2e0e2d6
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 298
    scopes: []
scopes: []
...

Required conditions of queue rule default for merge

• check-success = build

Required conditions to stay in the queue

None