Git Shadowtree, by Sebastian Szvetecz, creates a mirrored directory view of a Git working tree for Windows developers and administrators. It projects repository files into a separate folder so tools can operate without moving the original .git metadata. The app uses link-based mirroring to avoid duplicating content and preserves folder hierarchies, making it useful where build systems or legacy tools require alternate path layouts.

How Shadowtree projects a repository without copying data

Shadowtree builds a shadow directory by creating NTFS symbolic link trees that point back to the original working files, so no file data is duplicated on disk. The tool mirrors full directory hierarchies into a separate location while leaving the repository’s metadata in place. Typical outcomes are a mapped tree that looks like a normal checkout and a near-zero additional disk footprint, because links reference existing files instead of making copies.

What system requirements and privileges it needs

Shadowtree operates on Windows with NTFS and requires the ability to create symbolic links, which means administrative privileges or Developer Mode must be enabled. The tool is designed to work with the native file system, so file access uses standard NTFS semantics and delivers native performance. That dependency confines use to machines where NTFS link creation is permitted and supported.

Who benefits and what operational trade-offs to expect

Developers and system administrators who must present repository files to build tools or legacy software gain the most practical value, because the shadow exposes the working tree in an alternate path layout. The tool differs from multiple-working-tree solutions by not creating separate indexes; it simply reflects one working copy. A key trade-off is that edits in the mirrored view act on the original files, so operators must manage write access and workflow accordingly.

A practical choice for controlled build and legacy-tool scenarios

Git Shadowtree is a pragmatic option for Windows developers and administrators who need an alternate filesystem view of a repository for builds or legacy integrations. Use the tool inside controlled build sandboxes or CI agents to limit accidental edits to live working trees and to keep environment differences isolated from normal developer workflows. Recommended.