How to fix error: path depth exceeds maximum in Git

On Windows, enable Git's long path support globally:

git config --global core.longpaths true

For system-wide configuration (all users):

git config --system core.longpaths true

This tells Git to handle paths exceeding the traditional 260-character Windows limit.

On Windows 10 (version 1607+) or Windows 11, enable long path support at the OS level:

Via Registry:

1. Open Registry Editor (regedit)
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
3. Set LongPathsEnabled to 1
4. Restart your computer

Via Group Policy (Pro/Enterprise editions):

1. Open Local Group Policy Editor (gpedit.msc)
2. Navigate to Computer Configuration → Administrative Templates → System → Filesystem
3. Open "Enable Win32 long paths"
4. Set to "Enabled"
5. Restart your computer

Reduce the base path length by cloning closer to your drive root:

# Instead of:
# C:\Users\YourName\Documents\Projects\company\team\repo

# Use:
cd C:\
git clone https://github.com/user/repo.git

This reduces the overall path length for all files in the repository.

If the issue involves deeply nested submodules, use shallow cloning:

git clone --depth 1 --shallow-submodules --recurse-submodules <repository-url>

This limits the history depth and can reduce path complexity.

If you control the repository structure, refactor to reduce nesting:

- Move deeply nested files closer to the root
- Consolidate redundant directory levels
- Use symbolic links for shared resources instead of duplicating nested paths
- Consider restructuring build output directories

For example, instead of:

src/components/features/user/profile/settings/components/forms/inputs/

Use:

src/components/user-profile-settings/