Add more detail when importing projects from GitHub with error duplicateEntries
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Proposal
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.
- Link to request: ZD - 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