From 908dd63fdcfbc036948239c28c9702fbdc389b69 Mon Sep 17 00:00:00 2001 From: Rhys Arkins <rhys@arkins.net> Date: Tue, 28 Jan 2020 06:40:14 +0100 Subject: [PATCH] docs: fix absolute internal links --- docs/usage/faq.md | 2 +- docs/usage/node.md | 4 ++-- docs/usage/noise-reduction.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/usage/faq.md b/docs/usage/faq.md index 4f8fae84ab..9a502c4392 100644 --- a/docs/usage/faq.md +++ b/docs/usage/faq.md @@ -38,7 +38,7 @@ You may configure more than one in the above. ### Support private npm modules -See the dedicated [Private npm module support](private-modules/) page. +See the dedicated [Private npm module support](/private-modules/) page. ### Control renovate's schedule diff --git a/docs/usage/node.md b/docs/usage/node.md index d00c5eeb53..0a4050704e 100644 --- a/docs/usage/node.md +++ b/docs/usage/node.md @@ -29,7 +29,7 @@ When Renovate processes your project's repository it will look for the files lis ## Configuring Support Policy -Renovate supports a [`supportPolicy`](configuration-options/#supportpolicy) option that can be passed the following values and associated versions (current as of May 2019): +Renovate supports a [`supportPolicy`](/configuration-options/#supportpolicy) option that can be passed the following values and associated versions (current as of May 2019): **Default:** `lts` @@ -52,4 +52,4 @@ For example, to instruct Renovate to upgrade your project to the latest [Long-te It's best to define this support policy inside the `node` configuration object so that it is applied to all Node.js-related files. -For additional language support see the [`supportPolicy` documentation](configuration-options/#supportpolicy). +For additional language support see the [`supportPolicy` documentation](/configuration-options/#supportpolicy). diff --git a/docs/usage/noise-reduction.md b/docs/usage/noise-reduction.md index 6422491739..7ba71e6793 100644 --- a/docs/usage/noise-reduction.md +++ b/docs/usage/noise-reduction.md @@ -13,7 +13,7 @@ Of course, please keep in mind that people's definitions of "noise" may differ. To reduce noise, you can reduce the number of updates in total, and a good way to do that is via intelligent grouping of related packages. -As an example, our default `":app"` and `":library"` [presets](config-presets/) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate. For example, all `@angular/*` packages that are updated at the same time will be raised in a "Renovate angular monorepo packages" PR. And every package in the React monorepo will be grouped together in a React monorepo PR too. +As an example, our default `":app"` and `":library"` [presets](/config-presets/) include the rule `"group:monorepos"`, which means that "sibling" packages from known monorepos will always be grouped into the same branch/PR by renovate. For example, all `@angular/*` packages that are updated at the same time will be raised in a "Renovate angular monorepo packages" PR. And every package in the React monorepo will be grouped together in a React monorepo PR too. You may wish to take this further, for example you might want to group together all packages related to `eslint`, even if they come from separate repositories/authors. In that case you might add config like this: -- GitLab