From 26575231b3a77298c3a7c40a8016521548845594 Mon Sep 17 00:00:00 2001 From: Meysam Date: Sat, 30 Nov 2024 13:05:19 +0700 Subject: [PATCH] fix(docs): typo --- docs/usage/getting-started/private-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage/getting-started/private-packages.md b/docs/usage/getting-started/private-packages.md index 0e6eb2f0dbca41..4eda2aaf0a2ce8 100644 --- a/docs/usage/getting-started/private-packages.md +++ b/docs/usage/getting-started/private-packages.md @@ -36,7 +36,7 @@ However if you do still use them, private modules should work if you configure ` It is strongly recommended not to use private modules on a private registry and a warning will be logged if that is found. Credentials stored on disk (e.g. in `~/.npmrc`) are no longer supported. -The recommended way of using local presets is to configure then using "local" presets, e.g. `"extends": ["local>myorg/renovate-config"]`, and ensure that the platform token has access to that repo. +The recommended way of using local presets is to configure them using "local" presets, e.g. `"extends": ["local>myorg/renovate-config"]`, and ensure that the platform token has access to that repo. It's not recommended that you use a private repository to host your config while then extending it from a public repository. If your preset doesn't have secrets then you should make it public, while if it does have secrets then it's better to split your preset between a public one which all repos extend, and a private one with secrets which only other private repos extend.