287a857511
* Update packages landing page * Docs updates for Container reg GA * Update billing note * Delete CR feature preview files * Fix broken link * Remove github.ref from workflows See https://github.com/github/docs-internal/pull/19953 * Put 3rd party action message in a reusable * Update content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/learn-github-packages/deleting-and-restoring-a-package.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/working-with-a-github-packages-registry/migrating-to-the-container-registry-from-the-docker-registry.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/working-with-a-github-packages-registry/working-with-the-container-registry.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * Update content/packages/managing-github-packages-using-github-actions-workflows/publishing-and-installing-a-package-with-github-actions.md Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> * fix bug with wbr breaking a link inside a code tag inside a table * Make revisions suggested by Nilofer See https://github.com/github/docs-internal/pull/19987/files#r655014673 * Mention that migration is happening gradually * Reapply change suggested by Shayne * Fix punctuation * Remove bad link Co-authored-by: Lucas Costi <lucascosti@users.noreply.github.com> Co-authored-by: Sarah Schneider <sarahs@github.com> Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com> Co-authored-by: Melanie Yarbrough <11952755+myarb@users.noreply.github.com>
3.3 KiB
title, intro, product, redirect_from, permissions, versions
| title | intro | product | redirect_from | permissions | versions | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Viewing packages | You can see details about packages published to a repository, and narrow results by organization or user. | {% data reusables.gated-features.packages %} |
|
You must have at least read permissions to view a package. |
|
{% data reusables.package_registry.packages-ghes-release-stage %} {% data reusables.package_registry.packages-ghae-release-stage %}
About package views
Your ability to view a package depends on several factors. By default, you can view all packages you have published.
Repository-scoped packages inherit their permissions and visibility from the repository that owns the package. The registries below use this type of permissions:{% if currentVersion != "free-pro-team@latest" %}
- Docker registry (
docker.pkg.github.com){% endif %} - npm registry
- RubyGems registry
- Apache Maven registry
- NuGet registry
{% if currentVersion == "free-pro-team@latest" %} The Container registry offers you the option of granular permissions and visibility settings that can be customized for each package owned by a personal user or organization account. You can choose to use granular permissions or connect the package to a repository and inherit it's permissions. For more information, see "Connecting a repository to a package." {% endif %}
For more information, see "About permissions for GitHub Packages{% if currentVersion == "free-pro-team@latest" %}" and "Configuring a package's access control and visibility{% endif %}."
{% data reusables.package_registry.package-page-info %}
Viewing a repository's packages
You can find and view a package located in a particular repository.
{% data reusables.repositories.navigate-to-repo %} {% data reusables.package_registry.packages-from-code-tab %} {% data reusables.package_registry.navigate-to-packages %}
Viewing an organization's packages
You can find and view a package located in the repositories of an organization you belong to.
{% data reusables.profile.access_org %} {% data reusables.user_settings.access_org %} 3. Under your organization name, click {% octicon "package" aria-label="The package icon" %} Packages. {% data reusables.package_registry.navigate-to-packages %}
Viewing your packages
You can find and view any package you've published across all organizations and repositories.
{% data reusables.profile.access_profile %}
2. On the top of the profile page, in the main navigation, click Packages.
{% data reusables.package_registry.navigate-to-packages %}