File a do-epic chunk's findings and decisions in its epic, and give its judge the epic's records #623
Reference in New Issue
Block a user
Delete Branch "item-413"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A chunk do-epic runs can now file a finding as an issue of its epic (
do-epic <EPIC-KEY> --file) and record a decision in the epic's description (--record-decision). Its judge reads the epic's Scoring and Decisions before the repo's records, and a chunk without a repo gets them with the human's rules.Two chunks that record a decision at once take a lock in turn, and recording one decision twice keeps one. A label the scheduler doesn't read is refused.
Places the change touches without making them easier to read:
skills/larv-review/SKILL.md§3 → "Findings": the "Under do-epic" bullet is two sentences, since a worker under do-epic has to learn there thattodo.mdisn't where its epic finding goes.README.md, thedo_epic/entry: one sentence namesfindings.py, as the entry names each file of the package.WIP: File a finding and record a decision in a do-epic epic, and give the judge the epic's recordsto File a do-epic chunk's findings and decisions in its epic, and give its judge the epic's records