[mergify]

Note

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

What this draft tests

Mergify checks that #8089 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 9c31607
2. the 4 pull requests queued ahead of this batch, listed below, which bring the tip to 033668d
3. #8089, 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 #8089 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 4 pull requests ahead, so a failure here can come from them as much as from #8089. 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.

• #8077
• #8080
• #8084
• #8087 — shares the scope frontend

Metadata for CI tooling, read by mergify ci

---
all_scopes: false
checking_base_sha: 033668d5cfe1e29495f5a6878e2e246440814d6e
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 8089
    scopes:
      - frontend
scopes:
  - frontend
...

1 scope

• frontend

Required conditions of queue rule default for merge

• github-review-approved [🛡 GitHub branch protection]
  • performance: faster version table load in app for projects with a lot of game versions #8089
• 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]
  • performance: faster version table load in app for projects with a lot of game versions #8089
• any of [🛡 GitHub branch protection]:
  • check-success = Lint and Test
    • performance: faster version table load in app for projects with a lot of game versions #8089
  • check-neutral = Lint and Test
    • performance: faster version table load in app for projects with a lot of game versions #8089
  • check-skipped = Lint and Test
    • performance: faster version table load in app for projects with a lot of game versions #8089

Queue graph

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

graph LR
    ce8031f1eddc482e953a8638d843ab70["actionable-livaro-872ti9<br/>#8086<br/>scopes: app"]
    dc3ea6f6e9d244ceb9e92142b1ea42d5["concrete-painpoilane-fz3fw4<br/>#8087<br/>scopes: frontend"]
    0365016225fa40e5a6b526723ef78951["spare-rigotte-yr4ib4<br/>#8089<br/>scopes: frontend"]
    dc3ea6f6e9d244ceb9e92142b1ea42d5 --> 0365016225fa40e5a6b526723ef78951
    style 0365016225fa40e5a6b526723ef78951 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 472286c2477ac9435a321d5843b566ddf66a865f

Persistent

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

Latest commit

Environment	URL
staging	https://e5443472.frontend-staging.rinth.dev
production	https://1d0ff914.frontend.rinth.dev