Repository navigation
Add planning worktree setup targets - #16
Merged
Merged
Conversation
Adapt the Vlajmaji helper for fresh clones and planning worktree setup, with preservation checks and disposable-repository tests run in CI. Document the workflow and its branch-publication behavior for contributors. Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Billo AI <ai-engineering@billo.systems>
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.
Fresh clones currently need manual Git commands to attach the separate planning documents. Add
make planning(andplanning-worktreealias), adapting Vlajmaji's helper to fetch and attach planning history at.worktrees/planningwhile preserving the implementation checkout and staging index.The helper fast-forwards clean planning checkouts, preserves local-ahead commits, and refuses dirty, locked, divergent, or occupied targets. If no remote planning branch exists, it publishes an existing local planning branch or creates and publishes an empty orphan root. Contributor notes and Make help describe that behavior; the README is unchanged.
Add
make test-toolsand run it in the existing CI check job. Its 23 real-Git cases use disposable repositories and local bare remotes, including fresh clones, idempotence, preservation guards, rejected pushes, and retry recovery.Validation:
make formatCARGO_NET_OFFLINE=true make lintmake test-tools— 23 passed, 0 failedshellcheck --shell=bash scripts/planning-worktree.sh tests/test-planning-worktree.shgit diff --check