Skip to content

merge queue: checking #1486 on main (d727f87) - #1492

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

merge queue: checking #1486 on main (d727f87)#1492
mergify[bot] wants to merge 3 commits into
mainfrom
mergify/merge-queue/4b4fd9772b

Conversation

@mergify

@mergify mergify Bot commented Oct 15, 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 magnificent-painbio-w1o8if of the default queue, to test #1486 before it merges into main. Pushing to this branch or closing this pull request removes #1486 from the queue.

What this draft tests

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

  1. main at d727f87
  2. #1486, 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 #1486 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: d727f875696d241264abde8554a310e59cdefbe6
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1486
    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 15, 2026 03:49
@Cuarroc @claude
test(leitstand): expect the flow graph at /leitstand/fluss
202c7ab 
Red first: the route does not exist yet, so the flow graph, its tab link
and the empty hint are missing.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@Cuarroc @claude
feat(leitstand): add the Fluss tab at /leitstand/fluss
30b801b 
Mounts the flow graph (COMP-3-2) as a Leitstand tab beside Haupt and
Betrieb: one node per agent of the active project, edges from the agent
that started another. Reduced motion and the empty hint come from the
graph itself; an unread or unreadable board shows the offline state
instead of claiming "no agents".

Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::renders the flow graph at /leitstand/fluss and marks its tab as the current one
Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::shows the empty hint at /leitstand/fluss while no agent runs
Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::reaches Fluss from Haupt by its tab link
Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::does not claim an empty flow when the board cannot be read at /leitstand/fluss

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1486
8966748
@mergify mergify Bot closed this Oct 15, 2026
@mergify mergify Bot mentioned this pull request Oct 15, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/4b4fd9772b branch October 15, 2026 03:18
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