This commit was merged in pull request #637.
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- do-epic reads a team's own repo labels: a `[label-repos]` table in `~/.claude-projects/do-epic/config.toml` maps each such label to its repo, such as `twu-4 = "tenant-web-ui-4"`, and do-epic reads a mapped label as it reads `repo:<name>`. An issue a person filed a sub-task under is no longer split by repo: its sub-tasks run instead, each under a label of its own, and the team closes the issue.
|
||||
- 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
|
||||
|
||||
@@ -12,9 +12,8 @@
|
||||
|
||||
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||
| 448 | 0.13.0 | | | **Read a team's own repo labels as do-epic's picks, through a label table in its config, and treat an item that has sub-tasks as split, so planning never files sub-tasks beside the team's own.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 8 | 2.2 |
|
||||
| 452 | 0.13.0 | | | **Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.** | 3 | 2 | 2 | 5 | 5 | 1.6 by 7, 1.5 by 3 | 2.1 |
|
||||
| 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 |
|
||||
| 449 | 0.13.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.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 |
|
||||
| 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 |
|
||||
@@ -77,32 +76,6 @@
|
||||
|
||||
## Details
|
||||
|
||||
### 448. Read a team's own repo labels as do-epic's picks, through a label table in its config, and treat an item that has sub-tasks as split, so planning never files sub-tasks beside the team's own.
|
||||
|
||||
do-epic reads an item's repo only from a `repo:<name>` label. A team that labels each issue with its repo's name, or with a short name such as `twu-4` for `tenant-web-ui-4`, gets no issue counted as placed. Planning then predicts every open item's repos again and can file sub-tasks beside the ones the team filed, and the team's own sub-tasks never run. On TW-13503, nine items with 40 sub-tasks between them would have been split again, two of them under issues with open pull requests. docs/decisions.md → `do-epic: drives one Jira epic …` already says that on the first machine, an item's label that equals a repo's name names that repo.
|
||||
|
||||
- A table in do-epic's config.toml maps a team's label to a repo's name, such as `[repo-labels]` with `twu-4 = "tenant-web-ui-4"`. A label the table maps records a pick, as `repo:<name>` does, wherever a pick is read: planning, the scheduler, human tasks, findings, finishing and the chunk's own run.
|
||||
- An open item that has any sub-task counts as split. Planning never predicts its repos or files a sub-task under it, and the scheduler works it through its sub-tasks, as it does an item labelled `split-by-repo`.
|
||||
- Test it on the in-memory backend with an epic shaped as TW-13503: parents whose sub-tasks carry the team's labels, and an item labelled with a short name.
|
||||
- `scheduler.chunks` sits next to `start_chunks`, a place the comprehension seats found hard to follow; leave `chunks` easier to read than it was.
|
||||
|
||||
Touches:
|
||||
|
||||
- `bin/do_epic/repo_pick.py`: `recorded`, `of_label`
|
||||
- `bin/do_epic/split.py`: `split`, `finished`
|
||||
- `bin/do_epic/planning.py`: `planned`, `placed`, `answered`, `ranked_keys`
|
||||
- `bin/do_epic/scheduler.py`: `chunks`, `held_up`
|
||||
- `bin/do_epic/human_tasks.py`: `notifier_checkout` (small)
|
||||
- `bin/do_epic/finish.py`: `repo_of` (small)
|
||||
- `bin/do_epic/findings.py`: `written` (small)
|
||||
- `bin/do_epic/main.py`: `chunk_run` (small), `chunk_root` (small), `split_items_closed` (small)
|
||||
- `bin/do_epic/config.py`: `DoEpicConfig`, `load`
|
||||
- `bin/do_epic/test_repo_pick.py`
|
||||
- `bin/do_epic/test_split.py`
|
||||
- `bin/do_epic/test_planning.py`
|
||||
- `bin/do_epic/test_scheduler.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 452. Make do-epic's view of the Jira workflow settings: the statuses at which an issue unblocks the issues it blocks, and the moves the team's own automation makes, so do-epic makes none of those.
|
||||
|
||||
do-epic counts an issue as done only where Jira's status category is done, and moves a finished chunk's issue to done itself, by `jira-finish-transition`. On a team whose CI moves issues through the workflow, both are wrong. On TW, CI moves an issue to Code Review when its pull request opens, to Release Ready when it merges, and to Done when it is deployed. So do-epic would move an issue to Done before it is deployed, and would hold every blocked issue until the blocker is deployed, though the team wants blocked work to start once the blocker's pull request merges.
|
||||
|
||||
Reference in New Issue
Block a user