From 2878adce185ae943f64aecb9ba63c1ebc1180558 Mon Sep 17 00:00:00 2001 From: Joshua Lawrence Date: Tue, 21 Jan 2025 12:52:56 -0500 Subject: [PATCH] Clarifying documentation to indicate that GITHUB_TOKEN can be used to install packages associated with other private repositories --- data/reusables/package_registry/authenticate-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/reusables/package_registry/authenticate-packages.md b/data/reusables/package_registry/authenticate-packages.md index 1450842775c8..8cec986bd343 100644 --- a/data/reusables/package_registry/authenticate-packages.md +++ b/data/reusables/package_registry/authenticate-packages.md @@ -6,4 +6,4 @@ You can use a {% data variables.product.pat_v1 %} to authenticate to {% data var To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use: * `GITHUB_TOKEN` to publish packages associated with the workflow repository. -* A {% data variables.product.pat_v1 %} with at least `read:packages` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access). +* A {% data variables.product.pat_v1 %} with at least `read:packages` scope to install packages associated with other private repositories (`GITHUB_TOKEN` can be used if the repository is granted read access to the package. See [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)).