Repository navigation
Repo create should default to public #1270
Description
Activity
We chatted about this internally a bit; we think the best change here is to have
repo createact more like other commands. something like:$ gh repo create foo --public # ...creates repo $ gh repo create foo --private # ...creates repo $ gh repo create foo ? What visibility should this have? > Public Private # ...creates repoIf there is other info to collect we could have a final confirm step.
We have a "prompt when user's intent is hard to guess" approach that I think fits well here.
If someone wants to work on this that'd be just fine ✨ but do check in first so we can finalize the UX.
Just wanted to raise a point here that a lot of people do not know that or depend upon GitHub to add hyphens to the repo name automatically if it has whitespace of any sort. Maybe that is something that can also be looked into.
And keeping the third UI makes it cleaner since then people can do the following as people don't create repos that often so they can take a minute extra to create it and set it up properly.
$ gh rep create foo bar ? What did you mean by the following > foo-bar as one repo foo and bar as two repos
And proceed accordingly? Or a standard can be set/ change in CLI to create multiple repos through this.
Just a suggestion to consider since sometimes that hyphen naming automatically saves us and this will allow longer names to the repo through the cli.
$ gh repo create foo --public # ...creates repo $ gh repo create foo --private # ...creates repo $ gh repo create foo ? What visibility should this have? > Public Private # ...creates repoHi @vilmibm , just wanted to know if this is the finalised UX. Please let me know if there are more changes, or perhaps include more options as @Vishesh-Gupta suggested. I'd like to work on this.
Reacted by Mislav MarohnićI'm new to CLI, would love to take a crack at this if you haven't started @ShubhankarKG! 🍰 ☕
Reacted by Mislav MarohnićSure, either @ShubhankarKG or @raygervais please take a stab!
If someone wants to work on this that'd be just fine but do check in first so we can finalize the UX.
I myself couldn't proceed because the design wasn't finalised.
@ShubhankarKG now that you have the design, if you want to proceed I’ll find another item to work on. 💻 🍾
Your call
Hey @raygervais , as per #1396 and continuing my ongoing work in #1357 , I'd like to take this one. Thanks!
Reacted by Ray Gervais, Mislav Marohnić and Aliabbas Merchant
I think the
gh repo createcommand should default to public.I know it's how I work and expect it to work. Maybe it's a function of private repos being a new feature in the "free user" feature set. Obviously, if you want something private it would suck if it first went public, but when I use github I don't think "private" first.
Something to consider.