Repository navigation
feat: scripts/worktree.sh creates a ready worktree with one command - #389
Merged
Merged
Conversation
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
scripts/worktree.sh <branch>creates a ready worktree in one command: it fetchesorigin, adds<primary>.wt/<branch with / as ->on a new branch fromorigin/mainwith no upstream, and links the primary checkout's gitignored.envso integration tests in the worktree reach the configured endpoints. It works from the primary checkout and from inside any worktree of it.Review notes (two-axis review, a fix round, a final two-axis review):
git pushcannot targetmain), link.envonly when missing, a test for running from inside a worktree, test env stripped of inheritedGIT_*, fail fast atrev-parse.feat/aandfeat-amap to one path and git refuses the second. The "worktree already has.env" branch has no test:.envis gitignored here, so a fresh worktree never has one.Related issues
None.
Runtime evidence (required for ingest / retrieval / serving behavior)
Run for real in this repository, then both throwaway worktrees and branches removed:
Verification
uv run pytestpasses —tests/test_worktree_script.py3 passeduv run ruff format --check .anduv run ruff check .passdocker compose build mcppasses (Dockerfile / dependency changes) — N/AChecklist (core principles)
doc_rowsand theturnslane.envskip-testslabel justified)