worktree-data-sync

To synchronize non-git data between git worktrees, you can use a diff and apply approach that compares source and destination worktrees, then selectively overwrites or seeds missing managed files like datasets and caches without altering existing content.

Keeping symlinks and external data links consistent across parallel development branches requires discovering managed paths from Git ignore rules and external symlinks, then safely reconciling them to prevent missing links in destination worktrees.

You can copy generated outputs by using a seeding function that materializes missing managed files in the destination worktree from the source, ensuring existing content is preserved while selected results are applied.

Git worktree data synchronization can handle cloud placeholders by preserving them during the sync process, and it rejects unsafe path traversal to ensure secure filesystem access across source and destination directories.

Yes, you can compare source and destination data to identify differences and apply selected changes by overwriting or creating renamed copies, allowing for accurate reconciliation of renamed files between worktrees.

You need Python 3, Git worktree metadata, and filesystem access to run the bundled discovery and synchronization scripts, while pytest is an optional dependency specifically for running the included tests.