You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fpt Configuring a package's access control and visibility lists internal #46907
Under "Package Creation", choose whether you want to enable the creation of public , private , or internal packages.
(This should become or private)
To enable organization members to create internal packages that are visible to all organization members, click Internal. If the organization belongs to an enterprise, the packages will be visible to all enterprise members.
In addition to the features available with GitHub Team, GitHub Enterprise includes:
...
Deployment protection rules with GitHub Actions for private or internal repositories
...
Additional features such as internal repositories and repository rules.
This probably isn't limited to one page in the docs:
Hi! I’d be interested in making this documentation correction. I read the contributing guidelines and saw that existing issues should be marked with the help wanted label before contributors open a pull request.
Would this issue be suitable for an external contribution, and could it be marked help wanted if so? I’ll wait for confirmation before making any changes.
No, you have to wait for it to actually happen. Issues get stuck in a queue for the appropriate team to review, and after which someone from the team reviews it and makes comments / adds that label.
Activity
subatoi commentedon Nov 11, 2026
Thanks @jsoref, we'll get this reviewed by the appropriate team
Berciyal-Grace commentedon Nov 18, 2026
Hi! I’d be interested in making this documentation correction. I read the contributing guidelines and saw that existing issues should be marked with the
help wantedlabel before contributors open a pull request.Would this issue be suitable for an external contribution, and could it be marked
help wantedif so? I’ll wait for confirmation before making any changes.Thank you!
jsoref commentedon Nov 18, 2026
No, you have to wait for it to actually happen. Issues get stuck in a queue for the appropriate team to review, and after which someone from the team reviews it and makes comments / adds that label.
If it were otherwise, I'd have just made a PR.