storage

To audit git repository disk usage, you can scan your multi-repo environment to identify top repos by size, surface oversized files, and enumerate worktrees. This highlights disk hotspots and archival candidates for weekly cleanup decisions.

Disk bloat in multi-repo environments is caused by oversized git-tracked assets, heavy build folders, and nested worktree copies. Unmanaged growth of these elements slows builds and creates maintenance headaches in storage-constrained environments.

To find stale git worktrees taking up disk space, you can enumerate all worktrees across your repositories to reveal nested copies. This visibility guides targeted archival and dedup actions to reclaim storage.

Yes, you can identify oversized files and git-tracked assets across your repositories. Surfacing these large files helps you decide which assets are candidates for pruning or adopting Git LFS to reduce disk usage.

The best way to prioritize repository cleanup is to list top repos by size to identify the largest space users. You can then target heavy folders, oversized files, and stale worktrees for archival and dedup actions.