Drop the decision's citation of the item this chunk finishes

This commit is contained in:
2026-11-20 23:35:31 +01:00
parent b014bec299
commit 49d37891fe
+1 -1
View File
@@ -162,7 +162,7 @@ Valid while `~/.claude` is a checkout of this repo.
## epic-branch: an epic's chunks branch off and merge into a working branch its project's config names, without a person, and a person merges that branch into the default branch in one pull request
2026-11-20, lilleman's call in item 472. Serves goals 1 and 1.6: a team may rule that only a person merges into its default branch. Such a team was asked to merge once per chunk, and reviewed an epic as many small pull requests. With `epic-branch` set, the loop asks once per epic, and the team keeps its rule. Valid while that rule covers only a team's default and protected branches.
2026-11-20, lilleman's call. Serves goals 1 and 1.6: a team may rule that only a person merges into its default branch. Such a team was asked to merge once per chunk, and reviewed an epic as many small pull requests. With `epic-branch` set, the loop asks once per epic, and the team keeps its rule. Valid while that rule covers only a team's default and protected branches.
- **The setting.** `epic-branch` in a project's config is a template with `{epic}` for the epic's key, such as `"{epic}"`. Left out, everything works as before. Under chunk-preflight the key is that of the Jira epic `plan` names, so a plan kept in a file has no working branch. Under do-epic it is the key of the epic do-epic drives.
- **A chunk's base is recorded in git.** `git config branch.<chunk's branch>.chunk-base <epic's working branch>`, in the checkout's shared config (`git_repo.CHUNK_BASE`). `git_repo.default_ref` answers `origin/<epic's working branch>` on such a branch, so each tool that measures a chunk against its base reads the chunk's own commits. Deleting the branch removes the record.