Can't do git clean on windows, paths too long
See original GitHub issueSteps to reproduce
- Do a fresh clone on a windows box
- Build
- git clean -fdx (careful, see step 1)
Expected behavior
It works
Actual behavior
Warnings (1 of many shown below), not everything is cleaned
warning: Could not stat path 'test/dotnet-publish.Tests/bin/Debug/netcoreapp1.0/PortableAppWithIntentionalDowngradePublishesDowngradedManagedCode/
PortableTests/PortableAppWithIntentionalManagedDowngrade/bin/Debug/netcoreapp1.0/PortableAppWithIntentionalManagedDowngrade.deps.json':
Filename too long
Guessing CLI team doesn’t use Windows much 😁 @eerhardt have you seen this?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Filename too long in Git for Windows
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem in regedit and then set LongPathsEnabled to 1 . If you have Windows 10 Pro ...
Read more >Git checkouts fail on Windows with "Filename too long error
According to the msysgit wiki on GitHub and the related fix this error, Filename too long, comes from a Windows API limitation of...
Read more >3 Ways to Fix Git Clone "Filename too long" Error in ...
2. Filename too long - Solution 1 - Git Global Level · Update the git version to the latest from here. If you...
Read more >Filename too long when cloning a git repository on windows
Windows Run gpedit.msc · Navigate to: Computer Configuration | Administrative Templates | System | Filesystem | Enable Win32 long paths · Set state...
Read more >How to solve "filename too long" error in git (Powershell ...
Learn how to solve "commit failed, filename too long" error on git Windows. Problem. Windows does not properly support files and directories ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have used this for a while with success:
git config --system core.longpaths true
. @nguerrera if this does not solve it for you, please, re-activate.http://ourcodeworld.com/articles/read/109/how-to-solve-filename-too-long-error-in-git-powershell-and-github-application-for-windows
I haven’t tried it, but I’m hopeful 😃 Can you let us know if this works, @nguerrera ?