1
0
mirror of synced 2025-12-21 19:06:49 -05:00
Files
docs/content/packages/getting-started-with-github-container-registry/enabling-github-container-registry-for-your-organization.md
Jason Etcovitch caaee7a124 Update all files to use {% data %} (#15253)
* Add back changes from prior to purge

* Manually fix some invalid Liquid

* Updoot render-content

* Improve test messages to show correct output

* Run el scripto

* Pass the remaining test
2020-09-29 16:01:04 -04:00

1.5 KiB

title, intro, product, versions
title intro product versions
Enabling GitHub Container Registry for your organization In an organization, organization admins can allow organization members to publish public or private container images to {% data variables.product.prodname_github_container_registry %}. {% data reusables.gated-features.packages %}
free-pro-team
*

{% data reusables.package_registry.container-registry-beta %}

Before organization members can publish container images to {% data variables.product.prodname_github_container_registry %}, an organization admin must enable package creation.

{% data reusables.profile.access_profile %} {% data reusables.profile.access_org %} {% data reusables.organizations.org_settings %} {% data reusables.organizations.member-privileges %} 5. Under "Package creation", choose whether you want to enable the creation of public or private container images. - To enable organization members to create a public container image, click Public. - To enable organization members to create a private container image that is only visible to other organization members, click Private. You can further customize the visibility of a private container image. For more information, see "Configuring access control and visibility for container images."

![Options to enable public or private packages ](/assets/images/help/package-registry/package-creation-org-settings.png)