merge queue: checking #262 on main (f38b128), stacked on #298

[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch ardent-herbesprovence-ilqdxt of the default queue, to test #262 before it merges into main.

What this draft tests

Mergify checks that #262 still passes CI once combined with everything queued ahead of it. CI runs on this draft's code, built in this order:

1. main at f38b128
2. the pull request queued ahead of this batch, listed below, which brings the tip to dcfa403
3. #262, the pull request of this batch

The check is speculative: it assumes the pull requests ahead will merge, so it starts without waiting for them.

✨ Where it stands: closed

Pull request #298 ahead in the queue was removed (reason: checks failed).

Follow the default queue in the dashboard

What happens next

• Mergify closes this draft.
• #262 is still in the queue.

Tip

A red check is not necessarily caused by this batch. These checks run on a tip that also carries the commits of the pull request ahead, so a failure here can come from it as much as from #262. See only this batch's changes.

Queued ahead of this batch

This pull request entered the queue before this batch and is not part of it.

• #298

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: dcfa403ddff3831cc458bc266c54572d80969467
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 262
    scopes: []
scopes: []
...

Required conditions of queue rule default for merge

• check-success = build

Required conditions to stay in the queue

None