Skip to content

merge queue: checking #1711 on main (c89ec55) - #1748

Closed
mergify[bot] wants to merge 9 commits into
mainfrom
mergify/merge-queue/5f8095ec2d
Closed

mergify[bot] wants to merge 9 commits into
mainfrom
mergify/merge-queue/5f8095ec2d

Conversation

@mergify

@mergify mergify Bot commented Oct 20, 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-civet-0mm0xq of the default queue, to test #1711 before it merges into main. Pushing to this branch or closing this pull request removes #1711 from the queue.

What this draft tests

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

  1. main at c89ec55
  2. #1711, 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 #1711 into main and closes this draft.
Metadata for CI tooling, read by mergify ci
---
all_scopes: false
checking_base_sha: c89ec558f1eac57df5abb10aa08ac3b49f9cfa97
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1711
    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 9 commits October 18, 2026 19:04
Test-First: scripts/lib/plan-sync.test.mjs::a merged PR flips an in-progress row to Erledigt with the merge date
Test-First: scripts/lib/plan-sync.test.mjs::closed unmerged and open PRs are reported not rewritten
Test-First: scripts/lib/plan-sync.test.mjs::only the status cell changes other columns stay byte-identical
Test-First: scripts/lib/plan-sync.test.mjs::CLI defaults to dry run and writes atomically only after valid GitHub evidence
Co-Authored-By: GPT-6 <noreply@openai.com>
Test-First: scripts/lib/plan-sync.test.mjs::a merged PR flips an in-progress row to Erledigt with the merge date
Test-First: scripts/lib/plan-sync.test.mjs::closed unmerged and open PRs are reported not rewritten
Test-First: scripts/lib/plan-sync.test.mjs::only the status cell changes other columns stay byte-identical
Test-First: scripts/lib/plan-sync.test.mjs::CLI defaults to dry run and writes atomically only after valid GitHub evidence
Co-Authored-By: GPT-6 <noreply@openai.com>
No-Test: plan text only
Co-Authored-By: GPT-6 <noreply@openai.com>
The harness turn_context.model observed on 2026-10-18 is gpt-6.1-sol.
This refines the generic GPT-6 family attribution in the preceding three commits without rewriting their history.

No-Test: attribution metadata only
Co-Authored-By: gpt-6.1-sol <noreply@openai.com>
Test-First: scripts/lib/plan-sync.test.mjs::synchronized rows are done for existing PLAN consumers
Co-Authored-By: gpt-6.1-sol <noreply@openai.com>
Retain the complete old status cell after the existing originally marker so parsePlan reads the result as done and replay needs no special case.

Test-First: scripts/lib/plan-sync.test.mjs::synchronized rows are done for existing PLAN consumers
Test-First: scripts/lib/plan-sync.test.mjs::a merged PR flips an in-progress row to Erledigt with the merge date
Test-First: scripts/lib/plan-sync.test.mjs::closed unmerged and open PRs are reported not rewritten
Test-First: scripts/lib/plan-sync.test.mjs::only the status cell changes other columns stay byte-identical
Test-First: scripts/lib/plan-sync.test.mjs::CLI defaults to dry run and writes atomically only after valid GitHub evidence
Co-Authored-By: gpt-6.1-sol <noreply@openai.com>
Test-First: scripts/lib/plan-sync.test.mjs::a dependency PR in another column is neither listed nor required

Test-First: scripts/lib/plan-sync.test.mjs::a status cell that already starts with Erledigt is left unchanged

Co-Authored-By: GPT-6 <noreply@openai.com>
Test-First: scripts/lib/plan-sync.test.mjs::a dependency PR in another column is neither listed nor required

Test-First: scripts/lib/plan-sync.test.mjs::a status cell that already starts with Erledigt is left unchanged

Co-Authored-By: GPT-6 <noreply@openai.com>
@mergify mergify Bot closed this Oct 20, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/5f8095ec2d branch October 20, 2026 14:29
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