Home / Questions / 324628
Accepted
Ruslan López
Asked: 2020-01-27 20:50:57 +0800 CST 2020-01-27 20:50:57 +0800 CST

Problem cloning a project with git on windows: Filename too long

  • 772

I was trying to clone my open source project on Windows 10, but got the following error:

fatal: cannot create directory at 'node_modules/bower/node_modules/update-notifier/node_modules/latest-version/node_modules/package-json/node_modules/got/node_modules/duplexify/node_modules/end-of-stream/node_modules/once/node_modules /wrappy': Filename too long

warning: Clone succeeded, but checkout failed.

You can inspect what was checked out with 'git status'

and retry with 'git restore --source=HEAD :/'

The folder where I am trying to clone is:

C:\Users\MiNombreDeUsuarioQueNoTieneEspacios\IdeaProjects

Is there a way to enable long paths?

git

2 Answers

  1. Best Answer

    Based on this answer from iveqy I proceeded as follows:

    1.- I searched my Windows for the git installation path:

    C:\Program Files\Git\mingw64\etc

    Where a file called gitconfig is located , which has a structure like the following:

    [http]
    sslBackend = openssl
    sslCAInfo = C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
[diff "astextplain"]
    textconv = astextplain
[filter "lfs"]
    clean = git-lfs clean -- %f
    smudge = git-lfs smudge --skip -- %f
    process = git-lfs filter-process --skip
    required = true
[core]
    editor = \"C:\\\\Program Files\\\\Sublime Text 3\\\\subl.exe\" -w
    longpaths = false
[credential]
    helper = manager

    The part that we are interested in modifying at the core level is called longpaths , by default it is found falsehere, we can change it manually and save the changes or we can guide ourselves as indicated in the response through the following command:

    git config --system core.longpaths true

    I focused on the part of the solution, however the origin of the problem that is necessary to know in order to know in depth is obtained in the marked link that gave me the opportunity to grant this answer

    • 6

  2. It happens due to a general limitation of Windows that recognizes, by default, the length of paths up to 260 characters. One way to get git to recognize long paths is (As admin):

    git config --system core.longpaths true

    If it's just to clone the repository, without affecting the general git configuration

    git clone -c core.longpaths=true <repo-url>

    For Windows 10 to recognize long paths permanently, from the registry editor (regedit)

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem -> LongPathsEnabled: 1

    Filename too long in Git for Windows
    How to fix “Filename too long error” during git clone

    • 4