Repository navigation
CI: chain to the lowest open task above the merged one; T30 note for the closed PR #120 - #121
Merged
Merged
Conversation
… note PR #120 under T30 [skip ci] After #113 (T23) merged, the pipeline chained T24 with the task text that main still carried before #114 renumbered the tasks (PR #120, closed). The "Start the next task" step looked for exactly T(NN+1) and stopped when that id was closed, so T22 -> T24 would have needed a manual label once T22 merges. It now takes the lowest open task issue above the merged one and applies the same on-hold/external and triage checks. TASKS.md: note under T30 that the closed PR's branch holds a first draft. STATE.md section 8: what happened and how the chain resumes (label #22 claude:implement). Refs #120. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014NfiFN5Ukdcnbh87uff2Dg
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.
Pipeline fix after the T23 → T24 mis-chain, plus two notes.
[skip ci]; merge by hand. Refs #120.claude-pipeline.yml, "Start the next task": the step looked for exactlyT(NN+1)and stopped when that id had no open issue. With T23 closed ahead of T22, the T22 merge would have stopped the chain. It now takes the lowest opentaskissue whose id is above the merged one (jqon the title), then runs the unchangedon-hold/externaland triage checks. Checked offline on the current issue list: after T22 it selects T24 — Partitioned-inverse fused solve (solve_alg = "algo1", issue #82 solve half) #24 (then stops on itson-hold), after T24 it selects T25 — Split factorization: tiled SYRK, chunked TRSM, split regime-C fronts #25.task/T24-nd-tree-ordering-cache; the note says it is unreviewed and not checked against the T30 text.claude:implementby hand (nothing chains into T22), removeon-holdfrom T24 — Partitioned-inverse fused solve (solve_alg = "algo1", issue #82 solve half) #24 when T24 should follow.🤖 Generated with Claude Code
https://claude.ai/code/session_014NfiFN5Ukdcnbh87uff2Dg
Generated by Claude Code