Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
amirebrahimi opened this issue Oct 31, 2024 · 2 comments · Fixed by #10065
Closed

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

amirebrahimi opened this issue Oct 31, 2024 · 2 comments · Fixed by #10065
Labels
good first issue kind/feature Feature requests/implementations status/accepted Feature request accepted for the roadmap

Comments

@amirebrahimi
Copy link

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.

@amirebrahimi amirebrahimi added kind/feature Feature requests/implementations status/triage This issue needs to be triaged labels Oct 31, 2024
@dimbleby
Copy link
Contributor

make a merge request!

@amirebrahimi
Copy link
Author

amirebrahimi commented Jan 23, 2025

Thank you @alexprabhat99 and @abn

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue kind/feature Feature requests/implementations status/accepted Feature request accepted for the roadmap
Projects
None yet
3 participants