Skip to content

merge queue: checking #1581 on main (3ad56a8) - #1583

Closed
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/09d71d71bc
Closed

mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/09d71d71bc

Conversation

@mergify

@mergify mergify Bot commented Oct 15, 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 rapid-fondue-tx7wcb of the default queue, to test #1581 before it merges into main. Pushing to this branch or closing this pull request removes #1581 from the queue.

What this draft tests

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

  1. main at 3ad56a8
  2. #1581, 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 #1581 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: 3ad56a8a2c231d5f4d56730a00b26101c6b29d95
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1581
    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 3 commits October 15, 2026 19:31
…eQL #59)

The proof step checks out github.event.pull_request.head.sha; CodeQL
(actions/cache-poisoning/poisonable-step) could not see statically that it
never runs on schedule/workflow_dispatch. Add the explicit event check and
pin it in ci-shape for both red-first steps.

Test-First: scripts/test-ci-shape.sh::ci-shape fails when the proof step 'if' drops the pull_request event check
A single replace pass can re-assemble a comment opener, e.g. `<!<!---->-->`.
Move the strip into stripComments(), which repeats until stable and also
drops an unterminated opener.

Test-First: docs/diagrams/export-svg.test.mjs::stripComments leaves no comment opener behind
@mergify mergify Bot closed this Oct 15, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/09d71d71bc branch October 15, 2026 18:25
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