> Unfortunately a lot of GitHub's settings are pretty broad, so there's potential for unintended consequences
JFTR, for my own curiosity, I tested this in a GHE I am admin off, and flipping the setting does not seem to touch the visibility for existing private packages. Also, newly created packages from private repos are private by default and you have to manually toggle them to public, regardless of the availability of that visibility setting.
Bug 1949247 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Unfortunately a lot of GitHub's settings are pretty broad, so there's potential for unintended consequences
JFTR, for my own curiosity, I tested this in a GHE I am admin in, and flipping the setting does not seem to touch the visibility for existing private packages. Also, newly created packages from private repos are private by default and you have to manually toggle them to public, regardless of the availability of that visibility setting.