You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was not able to find an open or closed issue matching what I'm seeing
Setup
$ git --version --build-options
git version 2.12.0.windows.1
built from commit: d4baef1cdfef9de62d43f9682a98ba57adc842e4
sizeof-long: 4
machine: x86_64
Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver
Microsoft Windows [Version 6.1.7601]
What options did you set as part of the installation? Or did you choose the
defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
Path Option: CmdTools
SSH Option: OpenSSH
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Performance Tweaks FSCache: Enabled
Use Credential Manager: Enabled
Enable Symlinks: Disabled
Any other interesting things about your environment that might be related
to the issue you're seeing?
A business decision was made at the beginning of the project to include all node_modules as part of the repository. We are also running an inhouse git server.
Details
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
I am currently using PowerShell, but the error also occurs when using CMD, Git Bash and GitExtensions.
What commands did you run to trigger this issue? If you can provide a
If you don't mind I'm going to obscure our internal project name, I don't think it's relevant to outcome/reproducibility of the issue.
git clone ssh://server/path/to/repos/Project.git
cd .\Project
git checkout -b develop origin/develop
What did you expect to occur after running these commands?
Expectation was to have a tracked local develop branch checked out.
What actually happened instead?
The following error was reported:
$ > git co -b develop origin/develop
fatal: cannot create directory at 'ProjectMVC/node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/node_modules/validate-npm-package-license/node_modules/spdx-correct/node_modules/spdx-license-ids': No such file or directory
It should be noted that we have "git config --global --add core.longpaths true" and that the checkout command above succeeds when using git version 2.9.2.windows.1
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
As mentioned above, we are using an inhouse git server.
The text was updated successfully, but these errors were encountered:
Long paths between 248 and 260 characters were not handled
correctly since Git for Windows v2.11.1, which [is now
fixed](git-for-windows/git#1084).
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Setup
defaults?
to the issue you're seeing?
A business decision was made at the beginning of the project to include all node_modules as part of the repository. We are also running an inhouse git server.
Details
I am currently using PowerShell, but the error also occurs when using CMD, Git Bash and GitExtensions.
What commands did you run to trigger this issue? If you can provide a
If you don't mind I'm going to obscure our internal project name, I don't think it's relevant to outcome/reproducibility of the issue.
Expectation was to have a tracked local develop branch checked out.
The following error was reported:
$ > git co -b develop origin/develop
fatal: cannot create directory at 'ProjectMVC/node_modules/gulp-autoprefixer/node_modules/gulp-util/node_modules/dateformat/node_modules/meow/node_modules/normalize-package-data/node_modules/validate-npm-package-license/node_modules/spdx-correct/node_modules/spdx-license-ids': No such file or directory
It should be noted that we have "git config --global --add core.longpaths true" and that the checkout command above succeeds when using git version 2.9.2.windows.1
URL to that repository to help us with testing?
As mentioned above, we are using an inhouse git server.
The text was updated successfully, but these errors were encountered: