Skip to content

fix(dev): isolate Cargo targets per worktree - #197

Draft
johnmatthewtennant wants to merge 1 commit into
mainfrom
jtennant/per-worktree-cargo-targets
Draft

fix(dev): isolate Cargo targets per worktree#197
johnmatthewtennant wants to merge 1 commit into
mainfrom
jtennant/per-worktree-cargo-targets

Conversation

@johnmatthewtennant

@johnmatthewtennant johnmatthewtennant commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Summary

Berd currently directs every checkout and worktree on a machine to one Tauri Cargo target directory. Concurrent just dev, test, check, and Clippy processes then serialize on Cargo’s artifact lock.

Default Tauri Cargo output to each checkout’s ignored src-tauri/target directory on Unix and Windows, while preserving BERD_TAURI_CARGO_TARGET_DIR as an explicit override. Worktrees can now compile independently. Sharing dependency downloads and safely seeding compiler artifacts are separate concerns; this PR only removes target-directory contention.

Testing

From two separate Berd worktrees, run:

bash scripts/resolve-tauri-cargo-target-dir.sh

Each command resolves to that worktree’s own src-tauri/target. Setting BERD_TAURI_CARGO_TARGET_DIR still returns the explicit path unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant