From 76a3d287f53ae9a328cc7a01ebcdd93cef7ef483 Mon Sep 17 00:00:00 2001 From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com> Date: Sun, 11 Sep 2022 06:27:26 +0200 Subject: [PATCH] docs(configuration options): split list (#17718) --- docs/usage/configuration-options.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md index fcf898116b..c68fa5f272 100644 --- a/docs/usage/configuration-options.md +++ b/docs/usage/configuration-options.md @@ -2170,9 +2170,12 @@ What may happen if you don't set a `prHourlyLimit`: 1. You merge the onboarding PR to activate Renovate 1. Renovate creates a "Pin Dependencies" PR (if needed) 1. You merge the "Pin Dependencies" PR -1. Renovate creates every single upgrade PR needed, which can be a lot. This may cause: - - Renovate bot's PRs to overwhelm your CI systems - - a lot of test runs, because branches are rebased each time you merge a PR +1. Renovate creates every single upgrade PR needed, which can be a lot + +The above may cause: + +- Renovate bot's PRs to overwhelm your CI systems +- a lot of test runs, because branches are rebased each time you merge a PR To prevent these problems you can set `prHourlyLimit` to a value like `1` or `2`. Renovate will only create that many PRs within each hourly period (`:00` through `:59`). -- GitLab