Arjun Chaudhary
Arjun Chaudhary

Reputation: 2453

warning: Clone succeeded, but checkout failed

C:\Users\User\Desktop>git clone https://github.com/XXXXXXXXXX.git
Cloning into 'one-piece'...
remote: Counting objects: 5463, done.
remote: Compressing objects: 100% (3600/3600), done.
remote: Total 5463 (delta 1539), reused 5359 (delta 1438), pack-reused 0
Receiving objects: 100% (5463/5463), 5.08 MiB | 1.38 MiB/s, done.
Resolving deltas: 100% (1539/1539), done.
Checking connectivity... done.
warning: unable to access 'hackathon/node_modules/noble/node_modules/bluetooth-hci-socket/node_modules/usb
/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/readable-stream/
node_modules/core-util-is/lib/.gitattributes': Filename too long
fatal: cannot create directory at 'hackathon/node_modules/noble/node_modules/bluetooth-hci-socket/node_mod
ules/usb/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/are-we-there-yet/node_modules/readable
-stream/node_modules/process-nextick-args': Filename too long
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry the checkout with 'git checkout -f HEAD'

Upvotes: 15

Views: 39079

Answers (4)

Fazil Raza
Fazil Raza

Reputation: 141

In my case this is how I solved it:

  1. cd into the project directory and un-stage all staged files if any by running git reset
  2. undo all changes in the working directory by running git checkout *

After doing the two steps you should be able to see the project files.

Upvotes: 0

Amazing Aidan
Amazing Aidan

Reputation: 184

Also check that the repository does not contain a folder called 'con' or 'prn' as these are reserved folders in Windows but are allowed in MacOS.

eg. src/main/kotlin/con/ will break on a Windows machine

Upvotes: 0

Niroshan Ratnayake
Niroshan Ratnayake

Reputation: 3801

The following answer worked for me

  1. Open either cmd or git bash and run it as an administrator
  2. Give the following command on the cmd or git bash which you ran as an administrator above
git config --system core.longpaths true
  1. This will allow to access long file names globally
  2. Now you can clone the repositories without any issue with Filename too long

Upvotes: 4

Bala Krishnan
Bala Krishnan

Reputation: 580

Try this out:

git config --system core.longpaths true

Source

Upvotes: 32

Related Questions