Allow changing destination directory name of Cloned Gist Repositories

[JustinGrote]

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

[lostintangent]

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 😁

[JustinGrote]

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.

[lostintangent]

Got it. Thanks for sharing that detail!

[JustinGrote]

@lostintangent I noticed there hasn't been a release in a while but I'm a lot better at vscode extensions (I maintain the PowerShell extension) than I was when I filed this issue, and I'm willing to write a PR if you'd be willing to facilitate it.

I see it being a extension setting you check on, and it'll prompt you for your Repo name after you select the path, auto-populated with your description (sanitized for filesystems and spaces replaced with hyphens)

[lostintangent]

Yeah if you're down for creating a PR, that would be much appreciated.

I've been recently focusing my attention on https://gistpad.dev and https://npmjs.com/gistpad-mcp, and so any contributions on the VS Code extension are a huge help 🙏