merge queue: checking #7965 on main (7bac891), stacked on #7963, #7961 and #7964

[mergify]

Note

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

What this draft tests

Mergify checks that #7965 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 7bac891
2. the 3 pull requests queued ahead of this batch, listed below, which bring the tip to fee46bb
3. #7965, 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: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

• Once the pull requests ahead have merged, Mergify merges #7965 into main and closes this draft.
• If a pull request ahead fails or leaves the queue without merging, this batch is requeued and checked again on a new draft: these checks assumed it would merge.

Tip

A red check is not necessarily caused by this batch. These checks run on a tip that also carries the commits of the 3 pull requests ahead, so a failure here can come from them as much as from #7965. 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.

• #7963
• #7961
• #7964

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: fee46bb6d2acad805cf85c5113d58c0703e085f0
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 7965
    scopes:
      - app
scopes:
  - app
...

1 scope

• app

Required conditions of queue rule default for merge

• github-review-approved [🛡 GitHub branch protection]
  • fix: nonfatal app db backup fail #7965
• any of [🛡 GitHub branch protection]:
  • check-success = Lint and Test
  • check-neutral = Lint and Test
  • check-skipped = Lint and Test

Required conditions to stay in the queue

• github-review-approved [🛡 GitHub branch protection]
  • fix: nonfatal app db backup fail #7965
• any of [🛡 GitHub branch protection]:
  • check-success = Lint and Test
    • fix: nonfatal app db backup fail #7965
  • check-neutral = Lint and Test
    • fix: nonfatal app db backup fail #7965
  • check-skipped = Lint and Test
    • fix: nonfatal app db backup fail #7965

Queue graph

The diagram is not laid out in queue order, so a node's position says nothing about when it merges.

graph LR
    dc042587d0ba4b1d90a0b9d2704f7e36["near-liaison-0f0kwp<br/>#7965<br/>scopes: app"]
    559fb6af16da4eeeaceb299ef94de4bb["infallible-foie-6abumr<br/>#7960<br/>scopes: app"]
    dc042587d0ba4b1d90a0b9d2704f7e36 --> 559fb6af16da4eeeaceb299ef94de4bb
    style dc042587d0ba4b1d90a0b9d2704f7e36 fill:#6366f1,color:#fff

Loading

[github-actions]

Pull request changelog

App

Added

Changed

Deprecated

Removed

Fixed

Security

Website

Added

Changed

Deprecated

Removed

Fixed

Security

Hosting

Added

Changed

Deprecated

Removed

Fixed

Security

[github-actions]

Frontend previews

Last deployed commit is 24ec52cccbc2c1e617424224f2af7dcce59a9fe0

Persistent

Environment	URL
staging	https://pr-7972-staging-frontend.modrinth.workers.dev
production	https://pr-7972-frontend.modrinth.workers.dev
storybook	https://pr-7972-storybook.modrinth.workers.dev

Latest commit

Environment	URL
staging	https://git-24ec52cc-staging-frontend.modrinth.workers.dev
production	https://git-24ec52cc-frontend.modrinth.workers.dev
storybook	https://git-24ec52cc-storybook.modrinth.workers.dev