Plan task-bench: the MVP and Go in mutate-changes in 0.15.0, follow-ups in 0.16.0; drop item 467, move item 469 into 0.15.0 and push 0.16.0 to 0.23.0 one release later
CI / tests (pull_request) Has been cancelled
CI / tests (pull_request) Has been cancelled
This commit is contained in:
+1
-1
@@ -392,7 +392,7 @@ Valid while the later fixes per finished chunk, which `score-outcomes` and the r
|
||||
- A file outside the checkout is read as it stands, never as the default branch held it: release standing, chunk-preflight and loop-claude's routing read such a plan or changelog from disk.
|
||||
- chunk-preflight and loop-claude's routing learn that a release's items are all done from the plan's commits. A plan outside the checkout no longer names such a release, so the release after it reads as next, and only the last release of all gets a release review called due and is called ready to cut. Both tools say so on every run, and that the release reviews and the cuts are the human's to call (`bin/release_plan/release_standing.py`, `UNSEEN_RELEASES`).
|
||||
|
||||
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.22.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
|
||||
Messages keep each file's usual name, such as `todo.md`, as its label, since the config keeps the names. Revisit at 0.23.0, which plans the support for `score-outcomes`, the routing figures, the release standing and the owed scoring run.
|
||||
|
||||
## project config: `language` names the prose's language by its English name, and `commit-title`, `pull-request-title` and `branch` are brace templates over `{id}` and `{summary}`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user