5/2/2023 0 Comments Give macassistant permission![]() ![]() For registries that support granular permissions, packages are scoped to a personal account or organization, and the account associated with the package does not change when you transfer a repository.When you transfer a repository, GitHub may transfer the packages associated with the repository, depending on the registry the packages belong to. For more information, see " Transferring a repository." You can transfer a repository to another personal account or organization. " Publishing and installing a package with GitHub Actions"." Configuring a package's access control and visibility".When you create a GitHub Actions workflow, you can use the GITHUB_TOKEN to publish, install, delete, and restore packages in GitHub Packages without needing to store and manage a personal access token. Note: The ability for GitHub Actions workflows to delete and restore packages using the REST API is currently in public beta and subject to change. Upload and delete packages (along with write:packages, or delete:packages) Upload and publish packages to GitHub Packages For more information, see " Deleting and restoring a package."ĭownload and install packages from GitHub Packages The repo scope is also required for repo-scoped packages. To delete a package on GitHub, your personal access token (classic) must at least have the delete:packages and read:packages scope.To download and install packages from a repository, your personal access token (classic) must have the read:packages scope, and your user account must have read permission.To use or manage a package hosted by a package registry, you must use a personal access token (classic) with the appropriate scope, and your personal account must have appropriate permissions. For more information, see " Creating a personal access token." GitHub Packages only supports authentication using a personal access token (classic). For more information, see " Configuring a package's access control and visibility." PermissionĬan upload, download, and manage this package. If you are using a GitHub Actions workflow to manage your packages, you can grant an access role to the repository the workflow is stored in by using the Add Repository button under "Manage Actions access" in the package's settings. For packages scoped to an organization, you can give any person or team in the organization an access role. If you publish a package to an organization, anyone with the owner role in the organization also gets admin permissions to the package.įor packages scoped to a personal account, you can give any person an access role. When you publish a package, you automatically get admin permissions to the package. For more information, see " Selecting whether a package inherits permissions from a repository" and " Disabling automatic inheritance of access permissions in an organization." If you're the owner of an organization, you can disable the automatic inheritance of permissions for all new packages scoped to your organization. To access the package's granular permissions settings, you must remove the package's inherited permissions. Note: If you publish a package that is linked to a repository, the package inherits its permissions from the linked repository by default. ![]() ![]() For the list of registries that support granular permissions, see " About permissions for GitHub Packages."Īnyone with admin permissions to the package can also grant access permissions for the package that are separate from the permissions set at the organization and repository levels. Public packages allow anonymous access and can be pulled without authentication or signing in via the CLI. If a package belongs to a registry that supports granular permissions, anyone with admin permissions to the package can set the package to private or public. Visibility and access permissions for packages The following GitHub Packages registries only support repository-scoped permissions.įor other registries, you can choose to allow packages to be scoped to a user or an organization, or linked to a repository. For more information, see " Connecting a repository to a package." You can find a package scoped to a repository by going to the main page of the repository and clicking the Packages link to the right of the page. Permissions for repository-scoped packagesĪ repository-scoped package inherits the permissions and visibility of the repository in which the package is published. The following GitHub Packages registries support granular permissions. You can change the access control and visibility of the package separately from a repository that is connected (or linked) to a package. Packages with granular permissions are scoped to a personal account or organization. Granular permissions for user/organization-scoped packages The permissions for packages can be scoped either to a user or an organization or to a repository. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |