You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Clone to Repository saves as the gist GUID which can make it hard to identify
Describe the solution you'd like
When choosing "Clone Repository", offer a popup to name the repository folder in the target rather than the GUID it is typically assigned. This behavior could be toggled by a preference variable
Describe alternatives you've considered
Clone and then rename afterwards, however this is less desirable to the workflow
The text was updated successfully, but these errors were encountered:
Ah yeah, that's a great suggestion! In your case, do your gists have descriptions, that you'd want to use as the cloned folder name? At a minimum, we should definitely use the description if the gist has one, since the ID is pretty useless 😁
I normally give them descriptions, but it should still prompt with the description auto-populated, because my descriptions tend to be very verbose which I'm not sure if that's the norm or not:
EDIT: To be clear I wouldn't normally name the folders this, I'd name the folder MSITest or AzureNotifyChange etc.
Is your feature request related to a problem? Please describe.
Clone to Repository saves as the gist GUID which can make it hard to identify
Describe the solution you'd like
When choosing "Clone Repository", offer a popup to name the repository folder in the target rather than the GUID it is typically assigned. This behavior could be toggled by a preference variable
Describe alternatives you've considered
Clone and then rename afterwards, however this is less desirable to the workflow
The text was updated successfully, but these errors were encountered: