Skip to content

Expose git errors instead of printing a generic error message #9819

@amirebrahimi

Description

@amirebrahimi

Issue Kind

Change in current behaviour

Description

Currently, if there are any git errors when run as a subprocess, the following error will be presented to the user:
Failed to clone <git repo>, check your git configuration and permissions for this repository

Impact

This can be misleading to the user in one case we've found, which is when long filename support needs to be enabled. What would be ideal is if the error message from git is exposed to the user.

Workarounds

Enabling long filename support and setting git config --system core.longpaths true fixes the issue, but a user wouldn't know to do that unless they dug in further.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions