Skip to content

Commit bdc2419

Browse files
Apply suggestion from @Copilot
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 72dec67 commit bdc2419

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/code-security/how-tos/secure-at-scale/configure-organization-security/manage-usage-and-access/giving-org-access-private-registries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ You need to be an **organization owner** to set up access to private registries
4141
1. In the expanded list of secrets and variables, select **Private registries** to display the "Private Registries" page.
4242
1. Select **New private registry** to add access details for a private registry.
4343
1. Use the **URL** and **Type** fields to define the location and type of the registry:
44-
* **URL** is the location where you access the private registry. For example, to use the {% data variables.product.prodname_registry %} registry for NuGet: `https://nuget.pkg.github.com/OWNER/index.json`.
44+
* **URL** is the location where you access the private registry. For example, to use the {% data variables.product.prodname_registry %} registry for NuGet: `https://nuget.pkg.github.com/ORGANIZATION/index.json`, where `ORGANIZATION` is the name of your organization on {% data variables.product.github %}.
4545
* **Type** is the type of registry.
4646
1. Select either **Token** or **Username and password**, depending on the authentication method, then enter data into the appropriate fields.
4747
Some types of authentication tokens, such as a {% data variables.product.github %} {% data variables.product.pat_generic_title_case %}, are tied to a particular user identity. Select the **Username and password** option for these and enter the relevant username as **Username** and the token as **Password**.

0 commit comments

Comments
 (0)