Finish item 455 in the plan
CI / tests (pull_request) Successful in 4m33s

This commit was merged in pull request #638.
This commit is contained in:
Lilleman
2026-11-19 17:11:23 +01:00
parent 62b4825cea
commit 846d9cd197
2 changed files with 4 additions and 18 deletions
+4
View File
@@ -1,5 +1,9 @@
# Changelog
## Unreleased
- do-epic --file takes --blocked-by <KEY> and --parent <KEY>, so a chunk files the next pull request of a change as an issue that waits for the one before it; a chunk's first prompt says when to use them.
## 0.12.0
- loop-claude asks a headless claude whether a worker that went quiet before its result is stuck, and prints the verdict and appends it to stuck-workers.md, without killing anything.
-18
View File
@@ -17,7 +17,6 @@
| 449 | 0.13.0 | 448 | | **Record do-epic's repo picks and sub-task summaries in the team's own spelling, such as `core-4` and `core-4: Bygg …`, as its config sets them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 6 | 2.0 |
| 453 | 0.13.0 | | | **Make the issue types that do-epic and `todo-item add` file in Jira settings, since a Jira project such as TW has no Task type.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 5 | 1.8 |
| 450 | 0.13.0 | | | **Add `do-epic <EPIC-KEY> --dry-run`, which prints every Jira write planning would make and each chunk that would start, and makes none of them.** | 2 | 2 | 2 | 4 | 3 | 1.6 by 5 | 1.6 |
| 455 | 0.13.0 | | | **Let a chunk file a follow-up issue that its own issue blocks, with `do-epic --file --blocked-by` and `--parent`, so a change a repo ships as two pull requests gets an issue for each.** | 2 | 2 | 1 | 3 | 2 | 1.6 by 4 | 1.4 |
| 451 | 0.13.0 | | | **Add a project setting `merge = "human"`, under which a chunk leaves its pull request ready for a person to merge, and a do-epic chunk parks until the pull request is merged.** | 3 | 2 | 3 | 6 | 5 | 1.6 by 7 | 1.4 |
| 454 | 0.13.0 | | | **Start a do-epic chunk's issue as the team's board expects, by settings: assigned to the account do-epic works as, moved by a start transition and added to a board's active sprint.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4 | 1.1 |
| 446 | 0.14.0 | | question | **Kill the process a stuck check names where its verdict is `stuck`, once the human says the recorded verdicts match what they would have done.** | 2 | 2 | 3 | 5 | 3 | 1.5 by 3 | 1.0 |
@@ -180,23 +179,6 @@ Touches:
- `bin/do_epic/test_planning.py`
- `README.md`: `## Tools` (small)
### 455. Let a chunk file a follow-up issue that its own issue blocks, with `do-epic --file --blocked-by` and `--parent`, so a change a repo ships as two pull requests gets an issue for each.
One epic issue is one chunk and one pull request. Some repos ship a change as two pull requests in two releases, as Timewave's legacy repos do: first a pull request that pins and isolates today's behaviour, then the one that changes it, each with its own ticket and the first blocking the second. A chunk in such a repo can't file the second issue so that it waits for the first, so the human must split those issues by hand before the run.
- `do-epic <EPIC-KEY> --file` takes `--blocked-by <KEY>`, which links the new issue as blocked by that issue of the epic, so a chunk files its second step and finishes its own.
- `--file` also files a sub-task, with `--parent <KEY>`, where the chunk's issue is a sub-task of a split item, so the second step stays under the same item.
- The chunk's instructions say when to use it: where the repo's rules ask for a change to ship as more than one pull request.
Touches:
- `bin/do_epic/findings.py`: `parsed`, `written`, `instructions`, `USAGE`, `HELP`
- `bin/do_epic/backend/protocol.py`: `EpicStore` (small)
- `bin/do_epic/backend/jira.py`: `JiraEpic.file`
- `bin/do_epic/backend/fake.py`: `MemoryEpic.file` (small)
- `bin/do_epic/test_findings.py`
- `README.md`: `## Tools` (small)
### 451. Add a project setting `merge = "human"`, under which a chunk leaves its pull request ready for a person to merge, and a do-epic chunk parks until the pull request is merged.
Every chunk merges its own pull request with `chunk-pr merge`. Some teams forbid that: Timewave's conventions say never to merge a pull request without the human's explicit go-ahead for that pull request. The loop can't run in such a team's repos without breaking the rule, and `wait-for-approval` doesn't cover it, since a reviewer's approval is not the go-ahead to merge.