wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About
  • What is WinGet?

© 2026 winget.ragerworks.com

Loading...
Install Git Shadowtree using Winget - wingetCollections
  1. Go back
  2. Packages
  3. Git Shadowtree
Git Shadowtree logo

Git Shadowtree Sebastian Szvetecz

cli dotnet git git-extension shadow-repository worktree
Use this command to install Git Shadowtree:
winget install --id=Szv.GitShadowtree -e

Git Shadowtree is a Git extension designed to maintain a separate "shadow" repository alongside your main Git repository. This tool allows you to track specific files and directories in the shadow repository while excluding them from the working directory of the main repository. It provides a way to manage sensitive or project-specific content without cluttering the primary codebase.

Key Features:

  • Shadow Repository Management: Maintain a decoupled shadow repository that tracks defined sets of files and directories, such as agent documentation or other sensitive materials.
  • File Exclusion from Working Directory: Files tracked in the shadow repository are excluded from the main working directory, ensuring a clean and focused environment for development.
  • Worktree Support: Automatically provisions a shadow repository for each worktree created via git worktree add, with seamless synchronization through push/pull operations.
  • Integration with Winget: Can be installed via winget, simplifying setup and configuration.

Audience & Benefit: Ideal for developers working on complex or multi-repository projects to maintain separate tracking of specific files without affecting the main workflow. This tool streamlines the management of project-specific or sensitive content while keeping the primary repository clean and efficient.

README

Git Shadowtree is a tool that allows you to maintain a separate "shadow" repository alongside your main Git repository. The shadow repository can be used to track specific files and directories that you want to keep separate from the main repository, while still being able to track them in the shadow repository.

GitShadowtreeIllustration

Installation

Scoop

scoop install https://raw.githubusercontent.com/szv/git-shadowtree/main/scoop/git-shadowtree.json

Open a new terminal afterwards so the updated PATH takes effect, then use git shadowtree ….

WinGet

winget install Szv.GitShadowtree

Open a new terminal afterwards so the updated PATH takes effect, then use git shadowtree ….

Manual

  1. Download the latest release of Git Shadowtree from the releases page.
  2. Extract the downloaded archive to a directory of your choice.
  3. Add the directory containing the git-shadowtree executable to your system's PATH environment variable.
    Open a new terminal afterwards so the updated PATH takes effect, then use git shadowtree ….

Project Setup

Clone the remote shadow repository into your working repository:

git shadowtree clone

Configure your user name and email for the shadow repository:

git shadowtree config user.name "..."
git shadowtree config user.email "..."

Usage

The .shadowtree file contains patterns that specify which files and directories should be included in the shadow repository. You can edit this file to customize the contents of the shadow repository. Files matched by the patterns in the .shadowtree file will be included in the shadow repository and excluded from the working repository. This allows you to keep certain files and directories separate from the main repository while still being able to track them in the shadow repository.

Adding, Committing, and Pushing Changes

To add files to the shadow repository, simply add patterns to the .shadowtree file. For example, to include all files in the .agents directory, you can add the following pattern:

Versions
0.1.0
0.0.2
Website
github.com
License
Last updated
6/17/2026
Download latest version
.agents/

Before committing changes to the shadow repository, you need to stage the changes using the git shadowtree add command. This command will add the specified files to the staging area of the shadow repository. For example, to stage all changes in the shadow repository, you can run:

git shadowtree add .

After staging the changes, you can commit them to the shadow repository using the git shadowtree commit command. This command will create a new commit in the shadow repository with the staged changes.

git shadowtree commit -m "Update shadow repository"

Committing changes to the shadow repository will also exclude the committed files from the working repository, ensuring that they are only tracked in the shadow repository.

To push the changes from the shadow repository to the remote repository, you can use the git shadowtree push command. This command will push the commits from the shadow repository to the specified remote repository.

git shadowtree push

Pulling Changes

To pull changes from the remote shadow repository, you can use the git shadowtree pull command. This command will fetch the latest commits from the remote shadow repository and merge them into your local shadow repository. It will also update the exclusion of files in the working repository based on the updated shadow repository.

git shadowtree pull

Worktrees

git shadowtree init and git shadowtree clone install a post-checkout git hook. When you create a new worktree with plain git worktree add , the hook automatically provisions a shadowtree for that worktree (cloned from the primary worktree's shadowtree) and checks the tracked files into it. This means tools that create worktrees on their own (for example, agents) get the shadowtree files without any extra step.

Each worktree gets its own shadowtree, so changes are synced between worktrees through the remote via git shadowtree push / git shadowtree pull.

If you set up your shadowtree before this feature existed (no hook installed yet), install it once with:

git shadowtree install-hook

The hook is shared across all worktrees, so a single install covers every future git worktree add. An existing, non-managed post-checkout hook is left untouched (use --force to overwrite, or add the printed one-line call to your hook).