Skip to content

merge queue: checking main (ac6dc16), #12264, #12260 and #12259 together - #12271

Closed
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/24e7845772
Closed

merge queue: checking main (ac6dc16), #12264, #12260 and #12259 together#12271
mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/24e7845772

Conversation

@mergify

@mergify mergify Bot commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

🎉 This pull request has been checked successfully and will be merged soon. 🎉

Branch main (ac6dc16), #12264, #12260 and #12259 are queued together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #12259.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue rule default for merge:

Required conditions to stay in the queue:

---
checking_base_sha: 280cc1454d8a687f3ddfb82233837fc45cb13c1a
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 12259
    scopes: []
scopes: []
...

JulianMaurin and others added 6 commits July 29, 2026 16:49
An option whose schema property is a bare `$ref` to an untitled `$defs`
entry rendered an empty value type, since both renderers only read the
target's `title`. Expand the target instead, and name the keys of an
inline object shape so a union like `batch_size` reads as
"integer or `{min, max}`".

MRGFY-8297

Change-Id: I25ebe90e607c8227ad921b9fe9d8305801e1ef4f
Detection, `mergify tests show`, and the test search API surface only runs
from the repository's default branch; pull request runs are stored but feed
Prevention instead. A repository whose CI has only ever run on pull requests
therefore sees an empty Detection page with working uploads.

MRGFY-8295

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CCCgUbY1KiEvFJdvfc81a4
Change-Id: I408c578a358d2c2bf60387a6101af8c663eff888
Cover the three page-wide controls (repository selector, filters, breakdown),
including that Max Running Checks cannot be broken down by priority rule. State
the Max Running Checks reference line as the effective max_parallel_checks, and
that the retention limit also caps how far back the calendar goes.

Note --json on queue show, and that --verbose is a global flag.

Refresh the screenshot to match the prose: the previous capture predates the
Filters and Breakdown controls. Captured through the dashboard's Mirage mock, so
the organization, repository and account on screen are placeholders rather than
a real account.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GFgsMFh2jCDbWYmMyJfnyz
Change-Id: I733471ef7ceecd8015d673dbf1a6ed86a2f311ff
@mergify
mergify Bot deployed to Mergify Merge Protections July 30, 2026 11:15 Active
@mergify mergify Bot closed this Jul 30, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/24e7845772 branch July 30, 2026 11:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant