Describe the feature or problem you’d like to solve

gh-repo-clone will clone repos, but not the wiki repo associated with it. For example, if this repo had a wiki, then gh repo clone cli/cli works, and git clone https://github.com/cli/cli.wiki.git works, but gh repo clone cli/cli.wiki will give the error `GraphQL error: Could not resolve to a Repository with the name 'cli/cli.wiki

Is your feature request related to a problem? Please describe.
the most common flow I have (and, I think, a lot of people have this flow) is to do some work, commit it all, lather-rinse-repeat. So 'c' is smart in that it can ask me if I want to stage all when none are staged, but in the spirit of being a lazy-ass dev, I'd really like to have a config point where I could say "yes, I'm super-la

We have a bunch of features we can move from the Beta section to the permanent docs.

I think everything under https://www.netlifycms.org/docs/beta-features/ except i18n and Nested collections can be moved

It would make sense to move each feature at a time to make sure we're not cluttering the docs

Describe the feature or problem you’d like to solve

Microsoft released Windows Terminal Preview yesterday. It would be nice if GitHub Desktop was able to detect it.

Proposed solution

Adds an option to the shells available to use.

Additional context

N/A