Skip to content

merge queue: checking #1838 on main (9cc16b8), stacked on #1835 - #1841

Closed
mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/1ba00af0d0
Closed

mergify[bot] wants to merge 5 commits into
mainfrom
mergify/merge-queue/1ba00af0d0

Conversation

@mergify

@mergify mergify Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Note

This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch punchy-marron-4knz3t of the default queue, to test #1838 before it merges into main.

What this draft tests

Mergify checks that #1838 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 9cc16b8
  2. the pull request queued ahead of this batch, listed below, which brings the tip to 35e7150
  3. #1838, 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 #1835 ahead in the queue was removed (reason: pull request dequeued).

Follow the default queue in the dashboard

What happens next

  • Mergify closes this draft.
  • #1838 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 #1838. 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.

Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 35e7150c45057c71c6d2040f372a48440e4a6041
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1838
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = red-first
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
    • check-success = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
    • check-success = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
    • check-success = @github-actions/red-first
  • github-review-approved [🛡 GitHub repository ruleset rule main-pr-required-checks]
  • label != do-not-merge
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-neutral = @mergify/Mergify Merge Protections
    • check-skipped = @mergify/Mergify Merge Protections
    • check-success = @mergify/Mergify Merge Protections
Required conditions to stay in the queue

Cuarroc and others added 5 commits October 22, 2026 14:02
Exercise the public stripper with literal expected SVG strings and retain the observed removal behavior for malformed comment openers.

Test-First: docs/diagrams/strip-comments.test.mjs::stripComments preserves literal comment text in CDATA
Test-First: docs/diagrams/strip-comments.test.mjs::stripComments retains removal behavior outside CDATA

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Protect original CDATA spans before applying the existing fixed-point comment removal to surrounding markup. Ignore CDATA-looking text in real comments, and keep removing openers assembled by earlier removals.

Test-First: docs/diagrams/strip-comments.test.mjs::stripComments preserves literal comment text in CDATA
Test-First: docs/diagrams/strip-comments.test.mjs::stripComments retains removal behavior outside CDATA

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Exercise real SIGTERM and SIGHUP delivery plus a SIGBREAK process-event bridge through the public CLI entry. Measure the existing six-second and four-second drain totals while preserving failure output and ledger ownership checks.

No-Test: test-only coverage of correct existing stop wiring; no production defect or artificial red phase

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
@mergify mergify Bot closed this Oct 22, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/1ba00af0d0 branch October 22, 2026 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant