Filename too long in Git for Windows

Question

I m using Git-1 9 0-preview20140217 for Windows  As I know  this release should fix the issue with too long filenames  But not for me   Surely I m doing something wrong  I did git config core longpaths true and git add   and then git commit  Everything went well  But when I now do a git status  I get a list of files with Filename too long  for example   node modules grunt-contrib-imagemin node modules pngquant-bin node modules bin-wrapper node modules download node modules request node modules form-data node modules combined-stream node modules delayed-stream test integration test-handle-source-errors js  Filename too long   It is quite simple to reproduce for me  just create a Yeoman web application with the Angular generator   yo angular   and remove node modules from the  gitignore file  Then repeat the aforementioned Git commands   What am I missing here

User · Answer

You should be able to run the command  git config --system core longpaths true   or add it to one of your Git configuration files manually to turn this functionality on  once you are on a supported version of Git  It looks like maybe 1 9 0 and after

User · Answer

In Windows  you can follow these steps which worked for me   Open your cmd or git bash as an administrator    Give the following command either from cmd or git bash which you ran above as an administrator  git config --system core longpaths true   This will allow accessing long paths globally  And now you can clone the repository with no issues with long paths

User · Answer

TortoiseGit  Windows  For anyone using TortoiseGit for Windows  I did this   1  Right-click on the folder containing your project   Select TortoiseGit - gt  Settings   2  On the  quot Git quot  tab  click the button to  quot Edit local  git config quot    3  In the text file that pops up  under the  core  section  add  longpaths   true Save and close everything  then re-try your commit   For me  this worked  I hope this minimizes any possible system-wide issues  since we are not editing the global  gitconfig file  but rather just the one for this particular repository

User · Answer

Create  gitconfig and add   core  longpaths   true   You can create the file in a project location  not sure  and also in the global location  In my case the location is C  Users  name

User · Answer

Steps to follow  Windows    Run Git Bash as administrator Run the following command   git config --system core longpaths true  Note  if step 2 does not work or gives any error  you can also try running this command  git config --global core longpaths true  Read more about git config here

User · Answer

The better solution is enable the longpath parameter from Git   git config --system core longpaths true   But a workaround that works is remove the node modules folder from Git     git rm -r --cached node modules   vi  gitignore   Add node modules in a new row inside the  gitignore file  After doing this  push your modifications     git add  gitignore   git commit -m  node modules removed    git push

User · Answer

Git has a limit of 4096 characters for a filename  except on Windows when Git is compiled with msys  It uses an older version of the Windows API and there s a limit of 260 characters for a filename   So as far as I understand this  it s a limitation of msys and not of Git  You can read the details here  https   github com msysgit git pull 110  You can circumvent this by using another Git client on Windows or set core longpaths to true as explained in other answers   git config --system core longpaths true   Git is build as a combination of scripts and compiled code  With the above change some of the scripts might fail  That s the reason for core longpaths not to be enabled by default   The windows documentation at https   docs microsoft com en-us windows desktop fileio naming-a-file has some more information      Starting in Windows 10  version 1607  MAX PATH limitations have been   removed from common Win32 file and directory functions  However  you   must opt-in to the new behavior       A registry key allows you to enable or disable the new long path   behavior  To enable long path behavior set the registry key at   HKLM SYSTEM CurrentControlSet Control FileSystem LongPathsEnabled    Type  REG DWORD

User · Answer

You could also try to enable long file paths   If you run Windows 10 Home Edition you could change your Registry to enable long paths   Go to HKEY LOCAL MACHINE SYSTEM CurrentControlSet Control FileSystem in regedit and then set LongPathsEnabled to 1   If you have Windows 10 Pro or Enterprise you could also use Local Group Policies   Go to Computer Configuration   Administrative Templates   System   Filesystem in gpedit msc  open Enable Win32 long paths and set it to Enabled

User · Answer

This might help  git config core longpaths true  Basic explanation  This answer suggests not to have such setting applied to the global system  to all projects so avoiding --system or --global tag  configurations  This command only solves the problem by being specific to the current project  EDIT  This is an important answer related to the  quot permission denied quot  issue for those whom does not granted to change git settings globally

User · Answer

Move repository to root of your drive  temporary fix   You can try to temporarily move the local repository  the entire folder  to the root of your drive or as close to the root as possible   Since the path is smaller at the root of the drive  it sometimes fixes the issues   On Windows  I d move this to C   or another drive s root

User · Answer

If you are working with your encrypted partition  consider moving the folder to an unencrypted partition  for example a  tmp  running git pull  and then moving back

User · Answer

In a windows Machine  Run Command Prompt as administrator then run below command     git config --system core longpaths true

User · Answer

git config --global core longpaths true   The above command worked for me  Using  --system  gave me config file not locked error

User · Answer

Executing git config --system core longpaths true thrown an error to me       error  could not lock config file C  Program Files    x86  Git mingw32 etc gitconfig  Permission denied    Fixed with executing the command at the global level   git config --global core longpaths true

User · Answer

To be entirely sure that it takes effect immediately after the repository is initialized  but before the remote history is fetched or any files checked out  it is safer to use it this way   git clone -c core longpaths true  lt repo-url gt       -c key value      Set a configuration variable in the newly-created repository  this takes effect immediately after the repository is initialized  but   before the remote history is fetched or any files checked out  The key   is in the same format as expected by git-config1  e g     core eol true   If multiple values are given for the same key  each   value will be written to the config file  This makes it safe  for   example  to add additional fetch refspecs to the origin remote    More info

User · Answer

I had this error too  but in my case the cause was using an outdated version of npm  v1 4 28   Updating to npm v3 followed by  rm -rf node modules npm -i   worked for me  npm issue 2697 has details of the  maximally flat  folder structure included in npm v3  released 2015-06-25

[windows] Filename too long in Git for Windows

Examples related to windows

Examples related to git