Add worktree_setup configuration for bootstrapping new worktrees #167
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.
Overview
Adds the ability to bootstrap a worktree with commands + copy over files that are explicitly ignored. This is useful for getting your worktree into a working state for claude to be able to test things locally.
Might do better as a per-repo config, but wanted to keep the changes limited to the existing config. You can workaround this, as shown in the example, to only run commands when specific files exist.
Changes
worktree_setupconfig section with:copy_ignored: List of glob patterns for gitignored files to copyrun: List of commands to execute after worktree creationExample config
{ "worktree_setup": { "copy_ignored": [".env.local", "config/*.secret"], "run": ["[ -f package.json ] && pnpm install || exit 0", "cp .env.example .env"] } }