ws-store-setup

To configure gitignored files across worktrees, you need to analyze .gitignore patterns and apply tracking strategies like symlinking or copying to initialize a centralized store. This ensures consistent asset handling per repository or worktree.

The best way to manage ignored assets consistently is to initialize a ws store that determines tracking strategies, such as symlink versus copy, for each file. This centralizes configuration and streamlines setup across all existing worktrees.

You need a centralized store for gitignored files when you manage multiple worktrees or repositories and require consistent or per-worktree storage strategies for ignored assets, preventing manual configuration errors and tedious setup.

Choosing between symlink and copy strategies depends on whether your worktrees require shared access to the same gitignored asset or independent per-worktree copies. The setup process analyzes your .gitignore to propose the appropriate tracking strategy per file.

Yes, worktree store setup works with existing ignored files by analyzing your repository's current state and .gitignore patterns. It identifies candidate gitignored files and validates the ws store configuration across all existing worktrees.