Skip to content

merge queue: checking #1838 on main (5ad970f) - #1853

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

merge queue: checking #1838 on main (5ad970f)#1853
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/1f2649f80a

Conversation

@mergify

@mergify mergify Bot commented Oct 22, 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 moving-painbeurre-crl8kg of the default queue, to test #1838 before it merges into main. Pushing to this branch or closing this pull request removes #1838 from the queue.

What this draft tests

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

  1. main at 5ad970f
  2. #1838, 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 #1838 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: 5ad970f2814ce251cf86077c4b4a686c1d7a9865
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1838
    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 22, 2026 14:04
@Cuarroc @codex
test(denkraum): cover CLI stop signal drain budgets
1f4ee7a 
Exercise real SIGTERM and SIGHUP delivery plus a SIGBREAK process-event bridge through the public CLI entry. Measure the existing six-second and four-second drain totals while preserving failure output and ledger ownership checks.

No-Test: test-only coverage of correct existing stop wiring; no production defect or artificial red phase

Co-Authored-By: GPT-6.1 Sol <noreply@openai.com>
@Cuarroc @codex
docs: record R908 delivery and observed signal selftest failure
89e96c1 
Update the owned V16-FU-2 status and preserve unresolved sibling duties. Record the observed queue failure without claiming a timing cause or fix.

Plan-ID: V16-FU-2 / R908-FU-1
No-Test: Documentation maintenance only; original test behavior and bytes are unchanged.
Co-Authored-By: Codex (gpt-6.1-sol) <noreply@openai.com>
@mergify @mergify-commit-signer
Merge of #1838
e0a5ab6
@mergify mergify Bot closed this Oct 22, 2026
@mergify mergify Bot mentioned this pull request Oct 22, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/1f2649f80a branch October 22, 2026 22:28
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