adobe / adobe/aem-core-cif-components
Not able to clone repo in windows
- Dominant language
- Java
- Stars
- 109
- Forks
- 78
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 4
Description
### Expected Behaviour
Should be able to clone repo.
### Actual Behaviour
Not able to clone due to Filename too long.
#### Steps to Reproduce
1. Go to https://github.com/adobe/aem-core-cif-components
2. Click on Clone button and select Open with GitHub Desktop
#### Platform and Version
Windows
#### Logs taken while reproducing problem
`Cloning into 'C:\Users\aswaroop\Documents\GitHub\aem-core-cif-components4'... remote: Enumerating objects: 30846, done. remote: Counting objects: 100% (1989/1989), done. remote: Compressing objects: 100% (977/977), done. remote: Total 30846 (delta 722), reused 1466 (delta 496), pack-reused 28857 Receiving objects: 100% (30846/30846), 15.75 MiB | 3.98 MiB/s, done. Resolving deltas: 100% (13159/13159), done. warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir/.content.xml: Filename too long warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.319.319.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.319.319.png.dir/.content.xml: Filename too long warning: unable to access 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-components/featuredcategorylist.svg/_jcr_content/renditions/cq5dam.thumbnail.48.48.png.dir/.gitattributes': Filename too long error: unable to create file examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-sample-assets/catalog/product/bolo-sport-watch/wg01-bk-0.jpg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png: Filename too long fatal: cannot create directory at 'examples/ui.content/src/main/content/jcr_root/content/dam/core-components-examples/library/cif-sample-assets/catalog/product/bolo-sport-watch/wg01-bk-0.jpg/_jcr_content/renditions/cq5dam.thumbnail.140.100.png.dir': 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 :/'`
#### Workaound
Can set longpaths in git configs but not all developers/qa have admin access to do the changes.
Contributor guide
Research direction
Reproduce the clone through GitHub Desktop on Windows and inspect the listed checkout failures under examples/ui.content. The issue is done when the repository can be cloned and checked out successfully without requiring developers or QA to change system-wide Git settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- operating-systems, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100