|
|
|
@@ -6,18 +6,19 @@
|
|
|
|
|
|
|
|
|
|
`Bar = 0.1`
|
|
|
|
|
|
|
|
|
|
`Next ID = 457`
|
|
|
|
|
`Next ID = 458`
|
|
|
|
|
|
|
|
|
|
## Items
|
|
|
|
|
|
|
|
|
|
| ID | Release | Blocked by | Exempt | Item | L | E | I | R | S | Moves | Score |
|
|
|
|
|
|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
| 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 |
|
|
|
|
|
| 456 | 0.13.0 | 451 | | **Keep loop-claude from starting a chunk for an item whose pull request is ready and awaits a person's merge under `merge = "human"`.** | 2 | 2 | 2 | 4 | 4 | 1.6 by 5, 1.4 by 3 | 2.2 |
|
|
|
|
|
| 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 |
|
|
|
|
|
| 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 |
|
|
|
|
|
| 457 | 0.13.0 | 451 | | **Resume a chunk whose pull request awaits a person's merge once it no longer merges cleanly into the default branch, so the worker brings it level again.** | 3 | 2 | 2 | 5 | 4 | 1.6 by 4, 1.5 by 3 | 1.9 |
|
|
|
|
|
| 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 |
|
|
|
|
|
| 456 | 0.13.0 | 451 | | **Keep loop-claude from starting a chunk for an item whose pull request is ready and awaits a person's merge under `merge = "human"`.** | 3 | 2 | 2 | 5 | 5 | 1.6 by 5, 1.4 by 3 | 1.7 |
|
|
|
|
|
| 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 |
|
|
|
|
|
| 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 |
|
|
|
|
@@ -78,43 +79,6 @@
|
|
|
|
|
|
|
|
|
|
## Details
|
|
|
|
|
|
|
|
|
|
### 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.
|
|
|
|
|
|
|
|
|
|
- A project setting `merge` takes `chunk`, the default and today's behaviour, or `human`.
|
|
|
|
|
- Under `human`, `chunk-pr merge` levels the branch and marks the pull request ready, then leaves the merge to a person and exits saying the pull request awaits a person's merge.
|
|
|
|
|
- A do-epic chunk then parks on a new gate, `your merge`, shown in its window's name and in `--status` like any gate. It takes no slot, finishes once the forge reports the pull request merged, and still resumes when a reviewer comments.
|
|
|
|
|
- A loop-claude chunk ends with the pull request ready. The chunk settles how the item's `--finish` runs after a person merges it.
|
|
|
|
|
- `parked_through` in `bin/do_epic/main.py` is the place the comprehension seats found hardest to follow; leave it easier to read than it was.
|
|
|
|
|
|
|
|
|
|
Touches:
|
|
|
|
|
|
|
|
|
|
- `bin/project_config/settings.py`: `SCALARS` (small)
|
|
|
|
|
- `bin/chunk_pr/main.py`: `merged`, `merge_turn`
|
|
|
|
|
- `bin/chunk_pr/approval.py`: `awaited` (small)
|
|
|
|
|
- `bin/do_epic/gates.py`: `gate`, `Gate`
|
|
|
|
|
- `bin/do_epic/main.py`: `parked_through`
|
|
|
|
|
- `bin/do_epic/chunk_prompt.py`: `shipping`
|
|
|
|
|
- `bin/do_epic/test_gates.py`
|
|
|
|
|
- `bin/do_epic/test_main.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (small), `## Tools` (small)
|
|
|
|
|
|
|
|
|
|
### 456. Keep loop-claude from starting a chunk for an item whose pull request is ready and awaits a person's merge under `merge = "human"`.
|
|
|
|
|
|
|
|
|
|
Under `merge = "human"`, `chunk-pr merge` leaves a chunk's pull request ready, with its item finished only on the branch. Until a person merges it, the default branch's plan still holds the item, so `chunk-preflight` names it as the next item again. loop-claude then starts a cycle that can only run `chunk-pr merge` once more and end, and it does so every cycle until the merge.
|
|
|
|
|
|
|
|
|
|
- `chunk-preflight` passes over an item whose branch has an open pull request that isn't a draft, where the project's config sets `merge = "human"`, and says so in its facts.
|
|
|
|
|
- Where every remaining item of the release waits like that, loop-claude stops and says which pull requests await a merge.
|
|
|
|
|
- Once the pull request is merged, the next chunk's preflight runs `chunk-pr clean` for the worktree it left, or tells the worker to.
|
|
|
|
|
|
|
|
|
|
Touches:
|
|
|
|
|
|
|
|
|
|
- `bin/chunk_preflight/main.py`
|
|
|
|
|
- `bin/chunk_preflight/facts.py`: `item_lines`, `pulls_text`
|
|
|
|
|
- `bin/chunk_preflight/test_chunk_preflight.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (small)
|
|
|
|
|
|
|
|
|
|
### 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.
|
|
|
|
@@ -182,6 +146,44 @@ Touches:
|
|
|
|
|
- `bin/do_epic/test_split.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (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.
|
|
|
|
|
|
|
|
|
|
- A project setting `merge` takes `chunk`, the default and today's behaviour, or `human`.
|
|
|
|
|
- Under `human`, `chunk-pr merge` levels the branch and marks the pull request ready, then leaves the merge to a person and exits saying the pull request awaits a person's merge.
|
|
|
|
|
- A do-epic chunk then parks on a new gate, `your merge`, shown in its window's name and in `--status` like any gate. It takes no slot, finishes once the forge reports the pull request merged, and still resumes when a reviewer comments.
|
|
|
|
|
- A loop-claude chunk ends with the pull request ready. The chunk settles how the item's `--finish` runs after a person merges it.
|
|
|
|
|
- `parked_through` in `bin/do_epic/main.py` is the place the comprehension seats found hardest to follow; leave it easier to read than it was.
|
|
|
|
|
|
|
|
|
|
Touches:
|
|
|
|
|
|
|
|
|
|
- `bin/project_config/settings.py`: `SCALARS` (small)
|
|
|
|
|
- `bin/chunk_pr/main.py`: `merged`, `merge_turn`
|
|
|
|
|
- `bin/chunk_pr/approval.py`: `awaited` (small)
|
|
|
|
|
- `bin/do_epic/gates.py`: `gate`, `Gate`
|
|
|
|
|
- `bin/do_epic/main.py`: `parked_through`
|
|
|
|
|
- `bin/do_epic/chunk_prompt.py`: `shipping`
|
|
|
|
|
- `bin/do_epic/test_gates.py`
|
|
|
|
|
- `bin/do_epic/test_main.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (small), `## Tools` (small)
|
|
|
|
|
|
|
|
|
|
### 457. Resume a chunk whose pull request awaits a person's merge once it no longer merges cleanly into the default branch, so the worker brings it level again.
|
|
|
|
|
|
|
|
|
|
Under `merge = "human"` a pull request stays ready for hours or days while the default branch moves. A conflict, such as each branch holding its own changelog bullet or plan edit, or a branch protection that requires an up-to-date branch, then blocks the person who would merge it. Yet `gate` in `bin/do_epic/gates.py` reads only the draft state, the checks, the review decision and the waiting threads, so the window and `--status` keep saying `awaits your merge`, and nothing resumes the chunk unless a reviewer comments.
|
|
|
|
|
|
|
|
|
|
- Where `by_human`, `gate` reads the forge's mergeability before it returns the `your merge` gate: GitHub's `mergeable` and `mergeStateStatus`, Gitea's `mergeable`. No reader exists yet under `bin/forge/`; add one beside `open_pull` in `bin/forge/pulls.py`.
|
|
|
|
|
- A pull request that conflicts with the default branch, or is behind it where the branch protection requires an up-to-date branch, gives an `Open` whose news tells the worker to run `chunk-pr merge` again, which levels, pushes, waits for the checks and marks ready. Settle whether that rerun passes `--finish` again, since the items are already finished on the branch.
|
|
|
|
|
- GitHub reports `mergeable` as `UNKNOWN` while it computes it: that keeps the `your merge` gate until the next read, rather than resuming the chunk.
|
|
|
|
|
- State the new resume in `docs/decisions.md` → "Long gates".
|
|
|
|
|
|
|
|
|
|
Touches:
|
|
|
|
|
|
|
|
|
|
- `bin/do_epic/gates.py`: `gate` (small)
|
|
|
|
|
- `bin/forge/pulls.py`
|
|
|
|
|
- `bin/forge/test_forge.py`
|
|
|
|
|
- `bin/do_epic/test_gates.py`
|
|
|
|
|
|
|
|
|
|
### 453. 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.
|
|
|
|
|
|
|
|
|
|
do-epic and `todo-item add` file every new issue as a Task, the name `plan_store/jira_epic.py` sets as `ISSUE_TYPE`. A Jira project without a Task type, such as TW, whose types are Feature, Bug, Chore and Investigation, refuses each one. So `do-epic --file` fails there, and so does the epic's finishing, which files a release review for each repo.
|
|
|
|
@@ -200,6 +202,25 @@ Touches:
|
|
|
|
|
- `bin/do_epic/backend/test_jira.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (small)
|
|
|
|
|
|
|
|
|
|
### 456. Keep loop-claude from starting a chunk for an item whose pull request is ready and awaits a person's merge under `merge = "human"`.
|
|
|
|
|
|
|
|
|
|
Under `merge = "human"`, `chunk-pr merge` leaves a chunk's pull request ready, with its item finished only on the branch. Until a person merges it, the default branch's plan still holds the item, so `chunk-preflight` names it as the next item again. loop-claude then starts a cycle that can only run `chunk-pr merge` once more and end, and it does so every cycle until the merge.
|
|
|
|
|
|
|
|
|
|
- `chunk-preflight` passes over an item whose branch has an open pull request that isn't a draft, where the project's config sets `merge = "human"`, and says so in its facts.
|
|
|
|
|
- Where every remaining item of the release waits like that, loop-claude stops and says which pull requests await a merge.
|
|
|
|
|
- Once the pull request is merged, the next chunk's preflight runs `chunk-pr clean` for the worktree it left, or tells the worker to.
|
|
|
|
|
- Under `merge = "human"`, `chunk-pr merge --finish` finishes a plan kept in Jira, or a plan or changelog kept in the config's folder, at once, before the person merges; where the pull request is closed unmerged, the item stays finished. Settle whether loop-claude finishes such an item only after the merge.
|
|
|
|
|
- Under loop-claude nobody answers a reviewer's comment on a pull request that awaits a person's merge, since the chunk's run has ended. Settle who does, or say in README that the person asks for it.
|
|
|
|
|
|
|
|
|
|
Touches:
|
|
|
|
|
|
|
|
|
|
- `bin/chunk_preflight/main.py`
|
|
|
|
|
- `bin/chunk_preflight/facts.py`: `item_lines`, `pulls_text`
|
|
|
|
|
- `bin/chunk_preflight/test_chunk_preflight.py`
|
|
|
|
|
- `bin/chunk_pr/main.py`: `levelled_and_finished`, `finished` (small)
|
|
|
|
|
- `bin/chunk_pr/test_chunk_pr.py`
|
|
|
|
|
- `README.md`: `### Set up a project` (small)
|
|
|
|
|
|
|
|
|
|
### 450. 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.
|
|
|
|
|
|
|
|
|
|
`do-epic <EPIC-KEY>` writes to Jira before it starts any chunk: labels, sub-tasks, comments on a team's issues and a new backlog order. A person has no way to see those writes before they happen, so the first run on a team's epic is a gamble, and the writes can't be taken back in one step. On TW-13503 the first run would have filed duplicate sub-tasks and posted comments to the team.
|
|
|
|
|