<!--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=448760) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal When the importation of a repository to GitLab.com fails, the only error description available to the end user, reported at `https://gitlab.com/<project path>/-/import/new`, is somewhat terse and does not include the full error. For example: {width=40%} The only way to determine the root cause is by examination of Gitaly logs, which for GitLab.com would require a ticket raised with support. We could add the full `json.error_metadata.stderr (as seen in the log)` which would go a long way to enabling the end user to be self-sufficient, for example: ``` creating repository: cloning repository: exit status 128 error: object 83db39a8630e64c5200c0644126fc6f0bfe69e07: hasDotgit: contains '.git' fatal: fsck error in packed object fatal: fetch-pack: invalid index-pack output ``` <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->