Repository navigation
merge queue: checking #1625 on main (5667eea), stacked on #1624 - #1627
Closed
mergify[bot] wants to merge 9 commits into
Closed
mergify[bot] wants to merge 9 commits into
mergify[bot] wants to merge 9 commits into
Conversation
An unknown column or worker status still reads "Läuft", and a passed test still reads "Fertig" on card and flow node. These tests pin the fix through lampFor, AgentCard and FlowTab. Test-First: src/screens/leitstand/lamps/lampFor.test.ts::returns unknown for a column the map does not know Test-First: src/screens/leitstand/lamps/lampFor.test.ts::returns unknown for a worker status it does not know Test-First: src/screens/leitstand/lamps/lampFor.test.ts::a passed test is worded as a test result Test-First: src/screens/leitstand/AgentCard.test.tsx::a card of an unknown column shows no running lamp Test-First: src/screens/leitstand/flow/FlowTab.test.tsx::a node of an unknown column shows the same neutral lamp as the card Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
lampFor no longer falls back to "Läuft": a column outside COLUMN_FORM or a worker status other than running is the neutral unknown lamp (DS-T-02 form), on the card and the flow node alike. The proven lamp says "Test bestanden" plus the age of the test run (testedAt) instead of "Fertig", so green names its evidence. Which head was tested is not on BoardCard yet (seam work, out of scope). Deliberate test adaptations: the three "Fertig" expectations now read "Test bestanden"; lampFor calls pass the fixed clock. Regression-For: 17548fc Test-First: src/screens/leitstand/lamps/lampFor.test.ts::returns unknown for a column the map does not know Test-First: src/screens/leitstand/lamps/lampFor.test.ts::returns unknown for a worker status it does not know Test-First: src/screens/leitstand/lamps/lampFor.test.ts::a passed test is worded as a test result Test-First: src/screens/leitstand/AgentCard.test.tsx::a card of an unknown column shows no running lamp Test-First: src/screens/leitstand/flow/FlowTab.test.tsx::a node of an unknown column shows the same neutral lamp as the card Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drives gates.sh run plan-check on a fixture with a known finding and on a clean plan; red until the gate exists. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gate plan-check (node scripts/plan-check.mjs --offline) joins the lanes precommit, prepush, branchpush, linux and linux_1. Offline keeps GitHub and the events log out of the verdict (listed as NICHT GEPRUEFT). docs/decisions.md is now read by a gate, so lane-plan classifies it heavy. Test-First: scripts/lib/plan-gate.test.mjs::plan-check gate fails on a plan finding and passes on a clean plan Test-First: scripts/lib/plan-gate.test.mjs::plan-check gate runs in the local and the linux CI lanes Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The ", " separator of the passed-test word sat in lampFor.ts and tripped the hardcoded-UI-string ratchet. The whole wording is now one texts.ts template filled through the existing fill helper. Regression-For: 17548fc Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moves the planned DS-T-03 row of the pixel-factory table to the Z2 table (placement fixed by Root), so the ID stays unique (plan-model duplicate-id), and names #1624 in the note on own-PR rows. No-Test: plan row only Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This is a merge queue draft opened by Mergify. Nobody needs to act on it.
Mergify opened it for batch worldwide-painmie-rzvw9y of the
defaultqueue, to test #1625 before it merges intomain. Pushing to this branch or closing this pull request removes #1625 from the queue.What this draft tests
Mergify checks that #1625 still passes CI once combined with everything queued ahead of it. CI runs on this draft's code, built in this order:
mainat5667eea857d365The check is speculative: it assumes the pull requests ahead will merge, so it starts without waiting for them.
🎉 Where it stands: checks passed
CI passed on this draft.
Follow the
defaultqueue in the dashboardWhat happens next
mainand closes this draft.Tip
A red check is not necessarily caused by this batch. These checks run on a tip that also carries the commits of the pull request ahead, so a failure here can come from it as much as from #1625. See only this batch's changes.
Queued ahead of this batch
This pull request entered the queue before this batch and is not part of it.
Metadata for CI tooling, read by
mergify ciRequired conditions of queue rule
defaultfor mergecheck-success = gates (linux)check-success = gates (windows)check-success = red-firstgithub-review-approved[🛡 GitHub repository ruleset rulemain-pr-required-checks]label != do-not-mergemain-pr-required-checks]:check-success = @github-actions/gates (linux)check-neutral = @github-actions/gates (linux)check-skipped = @github-actions/gates (linux)main-pr-required-checks]:check-success = @github-actions/gates (windows)check-neutral = @github-actions/gates (windows)check-skipped = @github-actions/gates (windows)main-pr-required-checks]:check-success = @github-actions/red-firstcheck-neutral = @github-actions/red-firstcheck-skipped = @github-actions/red-firstmain-pr-required-checks]:check-neutral = @mergify/Mergify Merge Protectionscheck-skipped = @mergify/Mergify Merge Protectionscheck-success = @mergify/Mergify Merge ProtectionsRequired conditions to stay in the queue
-conflict-draftbase = maincheck-success = gates (linux)check-success = gates (windows)check-success = red-firstgithub-review-approved[🛡 GitHub repository ruleset rulemain-pr-required-checks]label != do-not-mergelabel = review-okmain-pr-required-checks]:check-success = @github-actions/gates (linux)check-neutral = @github-actions/gates (linux)check-skipped = @github-actions/gates (linux)main-pr-required-checks]:check-success = @github-actions/gates (windows)check-neutral = @github-actions/gates (windows)check-skipped = @github-actions/gates (windows)main-pr-required-checks]:check-success = @github-actions/red-firstcheck-neutral = @github-actions/red-firstcheck-skipped = @github-actions/red-firstmain-pr-required-checks]:check-neutral = @mergify/Mergify Merge Protectionscheck-skipped = @mergify/Mergify Merge Protectionscheck-success = @mergify/Mergify Merge Protections