<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=366619) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> When importing a project from GitHub (self-managed) and the error **duplicateEntries** is encountered e.g. ``` 2:fetch remote: "error: object g577af66177f8c2589a076g770gbf9c150a309b2: duplicateEntries: contains duplicate file entries\nfatal: fsck error in packed object\nfatal: fetch-pack: invalid index-pack output\n": exit status 128. ``` What additional information can be added to help identify the location of the object more quickly. A customer encountered this error, and after a considerable amount of time they were able to identify that the object location - a PR snapshot branch Quoting the customer > It would be nice if gitlab could print where exactly it found that object, since this was on the PR snapshot branch, it's quite hard to find, but pretty sure gitlab importer should know exactly what it was parsing when the issue happened. To identify the source of the error the customer used BFG repo cleaner: https://rtyley.github.io/bfg-repo-cleaner/ with feature flag: `--fix-filename-duplicates-preferring tree` Running it shows which PR has the duplicate. After switching to the branch and using `% git ls-tree g577af66177f8c2589a076g770gbf9c150a309b2` shows the files. <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> - Link to request: [ZD](https://gitlab.zendesk.com/agent/tickets/294198) - internal link - Priority: ~customer priority:: Low - Why interested: Migration from GitHub - Problem they are trying to solve: The error prevented the import, along with all of the metadata. - Current solution for this problem: - Impact to the customer of not having this: None, already resolved but would like to help others encountering the same error. - Questions: - PM to mention: @iganbaruch <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->