Skip to content

merge queue: checking #1735 on main (5fb3e5c) - #1736

Closed
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ce02e7f99a
Closed

merge queue: checking #1735 on main (5fb3e5c)#1736
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/ce02e7f99a

Conversation

@mergify

@mergify mergify Bot commented Oct 20, 2026 •
edited
Loading

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 unique-eclair-z2dh0b of the default queue, to test #1735 before it merges into main. Pushing to this branch or closing this pull request removes #1735 from the queue.

What this draft tests

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

  1. main at 5fb3e5c
  2. #1735, 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 #1735 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 5fb3e5cac20c398f6194732c54e7b8e7ece8cde2
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1735
    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 2 commits October 20, 2026 11:20
@Cuarroc @claude
docs(plan): sync DG-05 to merged #1722 and record retro reviews
cf2b3ec 
PLAN.md DG-05 becomes Erledigt (#1722, merge 87314b5, head fb2aed4,
main CI green). DG-00 records the Codex fix round state and that P1/P2
are covered by these rows. The 18.10. review incident note records the
retroactive second-family reviews of #1693/#1694/#1702/#1704/#1705.

No-Test: docs status sync only
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1735
ba0e487
@mergify mergify Bot closed this Oct 20, 2026
@mergify mergify Bot mentioned this pull request Oct 20, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/ce02e7f99a branch October 20, 2026 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@Cuarroc