Skip to content

merge queue: checking #1629 on main (b99efb7) - #1631

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

merge queue: checking #1629 on main (b99efb7)#1631
mergify[bot] wants to merge 4 commits into
mainfrom
mergify/merge-queue/c79343c2b9

Conversation

@mergify

@mergify mergify Bot commented Oct 16, 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 weathered-chaource-cilo1i of the default queue, to test #1629 before it merges into main. Pushing to this branch or closing this pull request removes #1629 from the queue.

What this draft tests

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

  1. main at b99efb7
  2. #1629, 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 #1629 into main and closes this draft.
Metadata for CI tooling, read by mergify ci 
---
all_scopes: false
checking_base_sha: b99efb7106d881d97920d1e5b3785108d8325304
previous_check_retries: []
previous_failed_batches: []
pull_requests:
  - number: 1629
    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 4 commits October 16, 2026 12:05
@Cuarroc @claude
test(leitstand): red test for the first step on the empty main view
5b94159 
DS-T-05: an empty board and a missing project leave the main view
without any next step. Both tests fail until the empty states carry
an action.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Cuarroc @claude
fix(design): DS-T-05 main view offers the first step
3e1075d 
The empty main view now carries the HonestState action it already
supports. Without a project it offers "Projekt anlegen" and opens the
Werkzeuge tab, the only place where the old sidebar's "Projekt
hinzufuegen" form is shown (the Einstellungen project tab only edits an
existing project). With a read, empty board it offers "Auftrag
einreihen" and opens the Betrieb tab with the queue form. Both actions
only navigate; nothing starts a worker.

Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::an empty board offers Auftrag einreihen and opens the Betrieb tab
Test-First: src/screens/leitstand/LeitstandRoute.test.tsx::without a project the main view offers Projekt anlegen

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Cuarroc @claude
docs(plan): DS-T-05 row below DS-T-01, true after merge
2ad770d 
Moves the planned DS-T-05 row from the Pixel-Fabrik table so the ID
stays unique (plan-check duplicate-id).

No-Test: documentation only

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mergify @mergify-commit-signer
Merge of #1629
1e629c1
@mergify mergify Bot closed this Oct 16, 2026
@mergify mergify Bot mentioned this pull request Oct 16, 2026
Merged
@mergify
mergify Bot deleted the mergify/merge-queue/c79343c2b9 branch October 16, 2026 11:22
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