|
|
|
|
|
by tailspin2019
1527 days ago
|
|
One thing I would personally really like is a bit more control around the creation of Public vs Private repositories in my enterprise (Cloud) account. Namely, I'd like to be able to stop myself (the org owner) from inadvertently creating a public repo, or at least make it much more difficult to make that mistake. I can do this for other users in my account (of which I have none), but not for myself as the org owner. I live in fear of clicking the wrong pixel one day and pushing private customer code to a "not meant to be public" repo. |
|