From 437ec069c9e0592955ed98c3d6c541127bf5bb75 Mon Sep 17 00:00:00 2001 From: Damien Cassou Date: Fri, 18 Oct 2024 17:36:46 +0200 Subject: [PATCH] Fix typo in guidance-for-the-configuration-of-private-registries-for-dependabot.md --- ...or-the-configuration-of-private-registries-for-dependabot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md b/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md index 44d234e926ca..f5d3593bfcc7 100644 --- a/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md +++ b/content/code-security/dependabot/working-with-dependabot/guidance-for-the-configuration-of-private-registries-for-dependabot.md @@ -318,7 +318,7 @@ If there is no global registry defined in a `.npmrc` file, you can set `replaces {% data reusables.dependabot.access-private-dependencies-link %} -For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc file`. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`. +For scoped dependencies (`@my-org/my-dep`), {% data variables.product.prodname_dependabot %} requires that the private registry is defined in the project's `.npmrc` file. To define private registries for individual scopes, use `@myscope:registry=https://private_registry_url`. Registries should be configured using the `https` protocol.