-
Notifications
You must be signed in to change notification settings - Fork 39
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
Status message after cloning showing hyphen (-) instead of slash (/) #95
Comments
Hi dear @TechAkayy. Actually it is an expected behavior we auto generate a heaman friendly name from full resolved repository. You can provide directory name like I am closing issue but if you feel there is something to improve, please ping me to reopen. |
Hi @pi0 Yes, that's correct. But I raised this issue about showing the source repo's name correctly. So, I would have expected the displayed message message to be - Successfully cloned TechAkayy/icones to TechAkayy-icones instead of.. Successfully cloned TechAkayy-icones to TechAkayy-icones Trivial one, what do you think. |
Hi. Checking back it again, it is actually correct behavior (well, kinda!). Templates when resolved, will get a name. In case of git repositories, name is normalized with CLI output shows resolved You might make a custom CLI to change this behavior. |
Thanks @pi0 for the detailed reply 👍🏽 |
Environment
Node: v18.12.1
Package: npx giget@latest
Reproduction
npx giget@latest gh:TechAkayy/icones
Describe the bug
Look closely at this screenshot:
Cloned repo - gh:TechAkayy/icones
Status message - Successfully cloned TechAkayy-icones to TechAkayy-icones
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: