docs(configuration options): style fixes for prPriority (#22467)

Co-authored-by: Rhys Arkins <rhys@arkins.net>
This commit is contained in:
HonkingGoose 2023-05-29 12:43:24 +02:00 committed by GitHub
parent b08fa0cf8b
commit eaf8f890c0
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -2767,11 +2767,20 @@ This is why we configured an upper limit for how long we wait until creating a P
## prPriority ## prPriority
Sometimes Renovate needs to rate limit its creation of PRs, e.g. hourly or concurrent PR limits. 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. 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. 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 ```json
{ {