File item 467: tell a do-epic worker the team's label for each repo

This commit is contained in:
Lilleman
2026-11-20 10:46:12 +01:00
parent aed6a84abc
commit 5fb0f95e0c
+14 -1
View File
@@ -6,7 +6,7 @@
`Bar = 0.1`
`Next ID = 467`
`Next ID = 468`
## Items
@@ -15,6 +15,7 @@
| 449 | 0.15.0 | | | **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.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 |
| 450 | 0.15.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 |
| 467 | 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 |
| 466 | 0.15.0 | | | **Have stability-reviewer check each parser that splits a field on a separator against a value that holds the separator.** | 1 | 2 | 2 | 3 | 2 | 1.1 by 3 | 1.2 |
| 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 |
| 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 |
@@ -130,6 +131,18 @@ Touches:
- `bin/do_epic/test_planning.py`
- `README.md`: `## Tools` (small)
### 467. 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`
### 466. Have stability-reviewer check each parser that splits a field on a separator against a value that holds the separator.
An outside reviewer found that an importer split a full address on its separator and took the last part as the leaf, though the leaf itself may hold the separator; the importer's own test fixture held such a value, and each such row was dropped with only a log line. Our stability pass read the function and its tests and didn't raise it, and no deterministic tool covers it: the mutation tool does not mutate that language, and a mutant would not show a wrong split. Add one line to the stability reviewer's checks: where the change splits text on a separator or strips a suffix, look in the fixtures and a sample of the source data for a field that holds the separator, and report a row the parse then misplaces or drops.