The gh repo create command right now has separate and potentially confusing behaviors when ran inside an existing local git repository vs. outside of it.

Bugs:

• Remote origin already exists "fatal:remote origin already exists" when creating repo #2166 Remote repository configured #893
• Can't create a new repo while within a repo Git initialization doesn't happen after creating a repo in a node.js app #2059
• Takes parent directory instead of current directory name gh create repo takes parent directory name if parent directory contains .git #2026
• Confusing prompt This will create 'your-repo-name' in your current directory. Continue? (Y/n) Confusing prompt for creating repos #1913 gh repo create: Despite not creating a directory, it is confirmed #2180 gh repo create improvements #2295 Update confusing prompt #2214 Clarify repo-create confirmation prompt #2507
• Do not offer INTERNAL visibility option if it's not supported on the platform Selectively display visibility options during repo create #2106
• Have repo create pick up the default branch setting on GitHub Have repo create pick up the default branch setting on GitHub #1810
• Repo create: local directory for new repo not created when non-interactive and --confirm repo create: local directory for new repo not created when non-interactive and --confirm #2587

Features:

• Ask to git init Ask to git init on repo create  #2099 Init repository when running "gh repo create" in existing directory #1280
• Specify the base dir for the new repo Letting the user specify the base init dir for the newly created repo #2077
• Create with gitignore and license files Ability to initialize repo with .gitignore and license #1907
• Expose more repository settings Expose more repository settings in repo create #995
• After initializing a repo with a template pull down changes "gh repo create --template" creates an empty repository locally #2290

Ref. #547