Include full Gitaly error message in the UI when repository import fails

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

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:

image

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
Edited Jul 29, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading