Finish item 468 in the plan
CI / tests (pull_request) Successful in 4m47s

This commit was merged in pull request #659.
This commit is contained in:
Lilleman
2026-11-20 13:47:24 +01:00
parent 92b0acb5c6
commit 3991b0276e
2 changed files with 2 additions and 14 deletions
+1
View File
@@ -2,6 +2,7 @@
## Unreleased
- do-epic names the team's own label for each repo, from the `[label-repos]` table, when it tells a chunk's worker how to file a finding or a release review, and keeps `repo:<name>` for a repo the table doesn't name.
- do-epic records a repo pick, and the summary of each sub-task it files, in the team's own spelling: a label from the `[label-repos]` table of its config, and a `sub-task-summary` template with `{label}` and `{Summary}`.
- 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.
- The stability reviewer checks each parser that splits text on a separator or strips a suffix against a value that holds the separator, and reports a row the parse misplaces or drops.
+1 -14
View File
@@ -15,9 +15,8 @@
| 469 | 0.15.0 | | | **Move a do-epic parent issue whose sub-tasks a person filed to Release Ready once every sub-task has landed, and to Done once every sub-task is done, by transitions its config names.** | 3 | 2 | 2 | 5 | 4 | 1.2 by 4, 1.5 by 4, 1.6 by 3 | 3.1 |
| 453 | 0.15.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 |
| 470 | 0.15.0 | | | **Start an epic's runnable issues in order of score alone, scoring each open issue that holds no scores, the ones people filed included, so Jira's backlog order no longer decides what starts.** | 3 | 2 | 2 | 5 | 5 | 1.2 by 4, 1.6 by 3 | 1.5 |
| 468 | 0.15.0 | | | **Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.** | 2 | 2 | 2 | 4 | 2 | 1.6 by 4 | 1.4 |
| 454 | 0.15.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 |
| 467 | 0.15.0 | 453, 454, 468, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 467 | 0.15.0 | 453, 454, 469, 470 | question | **Cut 0.15.0 as soon as items 449, 450, 453, 454, 468, 469 and 470 have merged, before its release review, and run that review in 0.15.1.** | 1 | 1 | 1 | 1 | 1 | | 0.0 |
| 446 | 0.16.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 |
| 462 | 0.16.0 | | | **Run under `mutate-changes` the tests that today fail in mutmut's copy of the tree, so a mutant of a line only they cover is killed.** | 2 | 1 | 2 | 3 | 3 | code health by 3 | 4.7 |
| 77 | 0.16.0 | | | **Teach `bin/metric-bench` Go and TypeScript, rerun it once two projects' comprehension histories name places, and bring into review only a metric that tracks the panel.** | 4 | 2 | 1 | 5 | 6 | 1.1 by 7, 1.4 by 7 | 2.1 |
@@ -151,18 +150,6 @@ Touches:
- `bin/do_epic/test_do_epic.py`
- `README.md`: `### Set up a project` (small)
### 468. Tell a do-epic worker the team's own label for each repo when it files a finding or a release-review issue, so those issues carry the label the team's board uses.
Item 449 makes do-epic record a repo pick, and each sub-task it files, under the team's own label from the `[label-repos]` table (`repo_pick.label_of(pick, team)`). The instructions do-epic gives a chunk's worker still name only `repo:<name>`: `LABELS` in `bin/do_epic/findings.py` (used in `HELP` at findings.py:31, in `instructions` at :48, and in `written`'s refusal at :99 and its reply at :105) and the `--file ... --label repo:<name> --label do-epic-release-review` command in `finish.task` at `bin/do_epic/finish.py:60`. A team whose board uses its own labels therefore still gets a finding or a release review labelled `repo:core-4` where it expects `core-4`.
Give both prompts the team's label for each repo of the table where the table names it (`repo_pick.team_label`, `also`), and keep `repo:<name>` for a repo the table doesn't name. `finish.task` already knows each repo that lacks its review, so it can name each one's label outright, as `label_of(Repo(name), team)` gives it. The README states the pick's spelling (`repo-rule.md`'s bullet) but not the finding's, so it needs no change.
Touches:
- `bin/do_epic/findings.py`: `LABELS`, `instructions` (small), `written` (small)
- `bin/do_epic/finish.py`: `task` (small)
- `bin/do_epic/test_findings.py`: `Instructions`
- `bin/do_epic/test_finish.py`: `TheFinishingChunksTask`
### 454. 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.
When a do-epic chunk starts, its issue stays as Jira holds it: unassigned, in New and outside the sprint. A team whose board shows who works on what, such as TW, where an issue being worked is assigned to the person, In Progress and in the active sprint, then sees nothing of the loop's work. Today each worker would have to do this by hand, from rules only some machines hold.