Skip to content

merge queue: checking #1438 on main (67dc46b) - #1441

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

merge queue: checking #1438 on main (67dc46b)#1441
mergify[bot] wants to merge 2 commits into
mainfrom
mergify/merge-queue/e372d93b38

Conversation

@mergify

@mergify mergify Bot commented Oct 14, 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 chocolaty-menthe-sh9n46 of the default queue, to test #1438 before it merges into main. Pushing to this branch or closing this pull request removes #1438 from the queue.

What this draft tests

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

  1. main at 67dc46b
  2. #1438, 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 #1438 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 67dc46be7e7e4eb4bc761851f532b4f3a61cfc5d
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1438
    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 14, 2026 14:53
@Cuarroc @claude
docs(known-issues): move closed KI-30 to Behoben and condense its nar…
a9a1831 
…rative

The KI-30 row was closed on 2026-10-09 but still sat in the Offen table and its
narrative filled ~175 lines. Move the row to Behoben, keep cause, fix and the
closing evidence (42 queue runs, run 37910399142) in a short section and point
to the last commit holding the full text.

No-Test: documentation only

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1438
6067e50
@mergify mergify Bot closed this Oct 14, 2026
@mergify
mergify Bot deleted the mergify/merge-queue/e372d93b38 branch October 14, 2026 14:25
@mergify mergify Bot mentioned this pull request Oct 14, 2026
Merged
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