From af806addae7a5cff7da5302990bcd028c151ce16 Mon Sep 17 00:00:00 2001 From: Vanessa Date: Thu, 14 Mar 2024 07:30:29 +1000 Subject: [PATCH] Packages docset - Fix broken anchor links (#49659) --- .../configuring-a-packages-access-control-and-visibility.md | 6 +++--- .../package_registry/auto-inherit-permissions-note.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md index e9eb0f6476..b54a01c052 100644 --- a/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md +++ b/content/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility.md @@ -48,7 +48,7 @@ If you publish a package in a registry that only supports repository-scoped perm ## Configuring access to packages for your personal account -If you have admin permissions to a package that's scoped to a personal account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[Visibility and access permissions for packages](#visibility-and-access-permissions-for-packages)." +If you have admin permissions to a package that's scoped to a personal account, you can assign read, write, or admin roles to other users. For more information about these permission roles, see "[About inheritance of access permissions](#about-inheritance-of-access-permissions)." If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams. @@ -60,7 +60,7 @@ The selected users will automatically be given access and don't need to accept a ## Configuring access to packages for an organization -If you have admin permissions to a package that is scoped to an organization, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[Visibility and access permissions for packages](#visibility-and-access-permissions-for-packages)." +If you have admin permissions to a package that is scoped to an organization, you can assign read, write, or admin roles to other users and teams. For more information about these permission roles, see "[About inheritance of access permissions](#about-inheritance-of-access-permissions)." If your package is private or internal and scoped to an organization, then you can only give access to other organization members or teams. @@ -134,7 +134,7 @@ For packages scoped to a personal account or an organization, to ensure that a { The specified repository does not need to be the repository where the source code for the package is kept. You can give multiple repositories workflow access to a package. {% ifversion packages-inherit-permissions %} -If you publish a package that is linked to a repository, {% data variables.product.prodname_actions %} workflows in the linked repository automatically get access to the package, unless your organization has disabled the automatic inheritance of access permissions. For more information, see "[About inheritance of access permissions and visibility](#about-inheritance-of-access-permissions-and-visibility)" above. +If you publish a package that is linked to a repository, {% data variables.product.prodname_actions %} workflows in the linked repository automatically get access to the package, unless your organization has disabled the automatic inheritance of access permissions. For more information, see "[About inheritance of access permissions](#about-inheritance-of-access-permissions)" above. {% endif %} {% note %} diff --git a/data/reusables/package_registry/auto-inherit-permissions-note.md b/data/reusables/package_registry/auto-inherit-permissions-note.md index 7008d7c329..b64667a6e0 100644 --- a/data/reusables/package_registry/auto-inherit-permissions-note.md +++ b/data/reusables/package_registry/auto-inherit-permissions-note.md @@ -2,7 +2,7 @@ {% note %} -**Note:** If you publish a package that is linked to a repository, the package automatically inherits the access permissions of the linked repository, and {% data variables.product.prodname_actions %} workflows in the linked repository automatically get access to the package, unless your organization has disabled automatic inheritance of access permissions. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#about-inheritance-of-access-permissions-and-visibility)." +**Note:** If you publish a package that is linked to a repository, the package automatically inherits the access permissions of the linked repository, and {% data variables.product.prodname_actions %} workflows in the linked repository automatically get access to the package, unless your organization has disabled automatic inheritance of access permissions. For more information, see "[AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility#about-inheritance-of-access-permissions)." {% endnote %}