Repository navigation
Add support for "INTERNAL" visibility in the repoCreate command #798
Description
Activity
Thanks for a great feature request!
My recommendation would be to add the check for internal between
PRIVATEandPUBLICso the visibility is descending. i.e. If a user submits both the public and internal flags, the repo will be public. If they submit neither, it will still be private.I don't anticipate that people will be including both
--publicand--internal, but if they do, I would lean to first respecting the most restrictive one (--internal). When inputs are ambiguous, I believe that software should choose the most conservative default, especially when it comes to permissions. Would you agree?Alternatively, we could just raise a usage error that
--publicand--internalare mutually exclusive.Reacted by Aliabbas Merchant and Derek DitchI would raise an error to the user that --public and --internal are mutually exclusive. That way it is obvious to the user that they selected conflicting options.
Describe the feature or problem you’d like to solve
The GraphQL API supports creating repos as "Internal" for plans that support it, but it is not currently implemented in the cli.
Proposed solution
I propose we add a new
repoCreateCmdflag calledinternalhere and default it tofalse. We can then update the logic here to add support for internal visibility. My recommendation would be to add the check for internal betweenPRIVATEandPUBLICso the visibility is descending. i.e. If a user submits both the public and internal flags, the repo will be public. If they submit neither, it will still be private.Additional context
If approved, I'd be happy to open a PR implementing this.