From eaf8f890c0dd85940ed97a31e1df125b7b0dcad7 Mon Sep 17 00:00:00 2001
From: HonkingGoose <34918129+HonkingGoose@users.noreply.github.com>
Date: Mon, 29 May 2023 12:43:24 +0200
Subject: [PATCH] docs(configuration options): style fixes for `prPriority`
(#22467)
Co-authored-by: Rhys Arkins <rhys@arkins.net>
---
docs/usage/configuration-options.md | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/docs/usage/configuration-options.md b/docs/usage/configuration-options.md
index 2e0b21d7fe..9cd4464fa2 100644
--- a/docs/usage/configuration-options.md
+++ b/docs/usage/configuration-options.md
@@ -2767,11 +2767,20 @@ This is why we configured an upper limit for how long we wait until creating a P
## prPriority
Sometimes Renovate needs to rate limit its creation of PRs, e.g. hourly or concurrent PR limits.
-In such cases it sorts/prioritizes by default based on the update type (e.g. patches raised before minor, minor before major).
+By default, Renovate sorts/prioritizes based on the update type, going from smallest update to biggest update.
+Renovate creates update PRs in this order:
+
+1. `pinDigest`
+1. `pin`
+1. `digest`
+1. `patch`
+1. `minor`
+1. `major`
+
If you have dependencies that are more or less important than others then you can use the `prPriority` field for PR sorting.
The default value is 0, so setting a negative value will make dependencies sort last, while higher values sort first.
-Here's an example of how you would define PR priority so that devDependencies are raised last and `react` is raised first:
+Here's an example of how you would define PR priority so that `devDependencies` are raised last and `react` is raised first:
```json
{
--
GitLab