microsoft / microsoft/Dynamics-365-FastTrack-Implementation-Assets

Filenames too long during gh clone

Open
#545 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
494
Forks
296
Avg merge
1d 10h
Merged PRs (30d)
5

Description

I chose a very short directory, but still getting this error:

C:\rp>gh repo clone microsoft/Dynamics-365-FastTrack-Implementation-Assets
Cloning into 'Dynamics-365-FastTrack-Implementation-Assets'...
remote: Enumerating objects: 12053, done.
remote: Counting objects: 100% (1419/1419), done.
remote: Compressing objects: 100% (519/519), done.
remote: Total 12053 (delta 1026), reused 929 (delta 900), pack-reused 10634 (from 4)
Receiving objects: 100% (12053/12053), 608.32 MiB | 52.20 MiB/s, done.
Resolving deltas: 100% (6048/6048), done.
error: unable to create file Customer Service/Field Service/Component Library/FSMobile/Service Report/solutions/FieldServiceReporting/Solution/Entities/BookableResourceBooking/FormXml/main/{32a79486-b187-4ab6-a6fe-f22a88b63261}_managed.xml: Filename too long
error: unable to create file Customer Service/Field Service/Component Library/FSMobile/Service Report/solutions/FieldServiceReporting/Solution/WebResources/_o25fs/BookableResourceBooking/FSReporting.BookableResourceBooking.Library.js.data.xml: Filename too long
Updating files: 100% (2290/2290), done.
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

failed to run git: exit status 128

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported gh repo clone command and the checkout failure for the two listed paths. The issue names no repository file or test; done would require a maintainer-defined change or documented resolution for checkout failures caused by these filenames.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.