Skip to content

merge queue: checking #1918 on main (be8b703) - #1921

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

merge queue: checking #1918 on main (be8b703)#1921
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/b4236178b5

Conversation

@mergify

@mergify mergify Bot commented Oct 26, 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 hot-tourte-vomriy of the default queue, to test #1918 before it merges into main. Pushing to this branch or closing this pull request removes #1918 from the queue.

What this draft tests

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

  1. main at be8b703
  2. #1918, 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 #1918 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: be8b70356ac888bfafdad6a7250a9155cdd77063
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1918
    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 26, 2026 02:15
@Cuarroc @claude
docs: add the v2.0 rest order and the GI05 answer to PLAN
36e868e 
Add the V2-REST section with rows for the Glass rest, V2-ACC1b-NEW,
V2-SHOT-BASE-PREP, V2-UAT-1a-NEW and V2-REL-PREP, the open endcard in
the decision inbox and the GI05 answer of 26.10.2026 (hide the 13
unconnected Glass areas by default, visible persistent switch). Correct
the KR-08c-2b-LIVE row to the evidenced merge (#1915, 5c15cdd).

Plan-ID: V2-REST-PLAN-PFLEGEN
No-Test: docs-only plan rows and recorded user decision
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Cuarroc @claude
docs: merge main (#1917) and correct the v2.0 rest order in PLAN
eb9e380 
Merge origin/main (be8b703, #1917) to resolve the real PLAN.md conflict
at the KR-08c-2b-LIVE / FU-KR08C-LIVE-PLACEMENT rows; both rows are kept.

Correct the V2-REST rows: own status after merge, #1917 merged with its
actual SHA, RESTORE next on a fresh base, exited-tab eligibility as a
separate residual, KR-07a parking kept in the 07a-11c-11d chain, GI05
runs independently of RESTORE. Record the bounded Root acceptance of
#1915 and #1917 and the GI05 answer versus the accepted conservative cut.

Plan-ID: V2-REST-PLAN-PFLEGEN
No-Test: docs-only plan correction, no runtime or test change
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1918
0b57748
@mergify mergify Bot closed this Oct 26, 2026
@mergify mergify Bot mentioned this pull request Oct 26, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/b4236178b5 branch October 26, 2026 03:35
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