[mergify]

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch benevolent-painseigle-x9dfzu of the default queue, to test #100 before it merges into main.

What this draft tests

Mergify checks that #100 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 c48ca37
2. the 2 pull requests queued ahead of this batch, listed below, which bring the tip to 52bb3d8
3. #100, 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

Merge queue reset: the base branch head moved outside the merge queue to f85f0c0.

Follow the default queue in the dashboard

What happens next

• Mergify closes this draft.
• #100 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 2 pull requests ahead, so a failure here can come from them as much as from #100. See only this batch's changes.

Queued ahead of this batch

These pull requests entered the queue before this batch and are not part of it.

• #98
• #99

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: 52bb3d8b23f6065c518aae812c1c81bfe72d5513
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 100
    scopes: []
scopes: []
...

Required conditions of queue rule default for merge

• check-success=CI: Test/Lint

Required conditions to stay in the queue

None

[mergify]

Merge queue reset: the base branch head moved outside the merge queue to f85f0c0