Skip to content

merge queue: checking #1835 on main (fa4f2d9) - #1848

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

mergify[bot] wants to merge 6 commits into
mainfrom
mergify/merge-queue/cc0ab168e9

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 varying-valencay-66aagw of the default queue, to test #1835 before it merges into main. Pushing to this branch or closing this pull request removes #1835 from the queue.

What this draft tests

Mergify checks that #1835 still passes CI on top of main. CI runs on this draft's code, built in this order:

  1. main at fa4f2d9
  2. #1835, the pull request of this batch

🎉 Where it stands: checks passed

CI passed on this draft.

Follow the default queue in the dashboard

What happens next

  • Mergify merges #1835 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: fa4f2d9a04db571918f8e5976d5b7b3680973ad9
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1835
    scopes: []
scopes: []
...
Required conditions of queue rule default for merge
  • check-success = gates (linux)
  • check-success = gates (windows)
  • check-success = 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-success = @github-actions/gates (linux)
    • check-neutral = @github-actions/gates (linux)
    • check-skipped = @github-actions/gates (linux)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/gates (windows)
    • check-neutral = @github-actions/gates (windows)
    • check-skipped = @github-actions/gates (windows)
  • any of [🛡 GitHub repository ruleset rule main-pr-required-checks]:
    • check-success = @github-actions/red-first
    • check-neutral = @github-actions/red-first
    • check-skipped = @github-actions/red-first
  • 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 6 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>
Assert literal public API output for CDATA-looking processing instruction content before real comments and genuine CDATA.

Regression-For: 417eec2

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Consume processing instructions as opaque spans before recognizing CDATA. Remove following markup comments and preserve genuine CDATA bytes. Reconcile only the FU-1015 plan row with the partial delivery and outstanding siblings.

Regression-For: 417eec2

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
Import the unchanged stripper test module from the existing export entrypoint. Preserve historical Test-First paths and all assertions.

No-Test: test wiring only, assertions unchanged

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/cc0ab168e9 branch October 22, 2026 19:07
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