This commit was merged in pull request #645.
This commit is contained in:
@@ -2,6 +2,7 @@
|
||||
|
||||
## Unreleased
|
||||
|
||||
- Under `merge = "human"`, `loop-claude` and `chunk-preflight` pass over an item whose ready pull request awaits a person's merge, and `loop-claude` stops, naming those pull requests, once every item left awaits one.
|
||||
- do-epic reads two new settings from a project's config: `jira-unblocking-statuses` names the statuses at which an issue unblocks the issues it blocks, and `jira-automation-moves-issues` leaves the move out of "In Progress" to the team's own automation.
|
||||
- The prose standard asks that a sentence about several named things holds for each of them.
|
||||
- `do-epic` resumes a chunk parked on `your merge` when its pull request no longer merges into its base, so the worker runs `chunk-pr merge` again to level the branch; a finished chunk in that state stays open until its pull request merges.
|
||||
|
||||
@@ -15,7 +15,6 @@
|
||||
| 463 | 0.14.0 | | defect | **Show the judge the transcript's tail whatever the size of the records.** | 2 | 2 | 3 | 5 | 3 | 1.2 by 6, 1.5 by 4, 1.4 by 2 | 4.2 |
|
||||
| 449 | 0.14.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.14.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 |
|
||||
| 457 | 0.14.0 | | | **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.14.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 |
|
||||
| 454 | 0.14.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.15.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 |
|
||||
@@ -127,38 +126,6 @@ Touches:
|
||||
- `bin/do_epic/backend/test_jira.py`
|
||||
- `README.md`: `### Set up a project` (small)
|
||||
|
||||
### 457. 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/forge/commands.py`
|
||||
- `bin/forge/pulls.py`
|
||||
- `bin/forge/test_forge.py`
|
||||
- `bin/release_plan/release_standing.py`: `chunk_item`, `picked`, `pick_from`
|
||||
- `bin/release_plan/next_chunk.py`: `planned`, `NoItem` (small)
|
||||
- `bin/release_plan/test_release_standing.py`
|
||||
- `bin/chunk_preflight/main.py`
|
||||
- `bin/chunk_preflight/gathered.py`: `Gathered`, `ItemFacts` (small)
|
||||
- `bin/chunk_preflight/facts.py`: `render`, `item_lines`, `pulls_text`
|
||||
- `bin/chunk_preflight/choices.py`
|
||||
- `bin/chunk_preflight/test_chunk_preflight.py`
|
||||
- `bin/loop_claude/routed_item.py`: `routed_item`
|
||||
- `bin/loop_claude/loop/chunk_start.py`: `plan_item`
|
||||
- `bin/loop_claude/test_routed_item.py`
|
||||
- `bin/loop_claude/loop/test_chunk_start.py`
|
||||
- `bin/deploy_release/cut.py`: `ready_release` (small)
|
||||
- `bin/chunk_pr/main.py`: `levelled_and_finished`, `finished` (small)
|
||||
- `bin/chunk_pr/test_chunk_pr.py`
|
||||
- `README.md`: `### Set up a project` (small), `## Tools` (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.
|
||||
|
||||
Reference in New Issue
Block a user