Repository navigation
Fix yolo linked-branch timing and branch recovery in plan-lifecycle - #77
Merged
DocksDocks merged 1 commit intoOct 19, 2026
Conversation
The contract's Linked branch intro now points to the Yolo runs timing and worktree rules, and the Yolo runs table has a Linked-branch timing row. Yolo recovery reads the branch with gh pr view --json headRefName once GitHub drops the linked branch after the pull request opens. Closes #76
DocksDocks
deleted the
76-fix-yolo-linked-branch-timing-and-branch-recovery-in-plan-lifecycle
branch
October 23, 2026 20:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
plan-contract.mdLinked branch: the intro now says a yolo run uses the timing and worktree rules in Yolo runs. The Yolo runs table gains aLinked-branch timingrow (right afternew, while drafting). Item 2 returns to its pre-yolo text.yolo/SKILL.mdRecover after compaction: after the pull request exists, read its number fromclosedByPullRequestsReferences, then the branch fromgh pr view <pr> --json headRefName. GitHub drops the linked branch fromgh issue develop --listonce a pull request exists.Verification
node scripts/ci.mjs --plugin plan-lifecycle: exit 0.content-hash --check-only: exit 0.After merge
plan-lifecycle0.13.1, then./docks-kit sync omp(asked separately).Closes #76