From 1e98ebbd3b23e1eb633546d22e5db1a811297425 Mon Sep 17 00:00:00 2001 From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Date: Fri, 7 Jun 2024 19:00:05 +0200 Subject: [PATCH] docs: update preset name in creating/editing Renovate presets (#29505) --- docs/development/creating-editing-renovate-presets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/development/creating-editing-renovate-presets.md b/docs/development/creating-editing-renovate-presets.md index 52779b6fd8..01de6485a9 100644 --- a/docs/development/creating-editing-renovate-presets.md +++ b/docs/development/creating-editing-renovate-presets.md @@ -16,7 +16,7 @@ Follow the rules below to increase the chance that your pull request gets merged We have multiple kinds of `group:` presets, with different rules. -##### Rules for `group:monorepo` preset +##### Rules for `group:monorepos` preset 1. Only group dependencies that _must_ be updated together @@ -27,7 +27,7 @@ We have multiple kinds of `group:` presets, with different rules. ##### Rules for `group:*` presets 1. Finally, any other `group:*` presets can be added if they are beneficial to a wide number of users -1. They don't need to be added to `group:recommended`, meaning that users will "opt in" to them one-by-one and _not_ get them automatically from `config:recommended`, which includes `group:monorepo` and `group:recommended` +1. They don't need to be added to `group:recommended`, meaning that users will "opt in" to them one-by-one and _not_ get them automatically from `config:recommended`, which includes `group:monorepos` and `group:recommended` #### Rules for replacement presets -- GitLab