renovate/renovate
1
0
Fork 0
mirror of https://github.com/renovatebot/renovate.git synced 2025-01-11 14:36:25 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5

docs: use number for count nouns (#14066)

Browse source
This commit is contained in:
HonkingGoose 2022-02-07 15:59:54 +01:00 committed by GitHub
parent 55ff7fb381
commit 673f1b0874
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/development/minimal-reproductions.md
View file

@ -42,7 +42,7 @@ If it's so simple then it shouldn't take you much time to commit it to a repo.
A good minimal reproduction:
- Uses the fewest amount of repository files and dependencies possible
- Uses the fewest number of repository files and dependencies possible
- Reduces the Renovate config to the minimum necessary
- Contains a `readme.md` file that explains current behavior and expected behavior

6
docs/usage/configuration-options.md
View file

@ -257,7 +257,7 @@ Configuring this to `true` means that Renovate will detect and apply the default
## branchConcurrentLimit
By default, Renovate won't enforce any concurrent branch limits.
The `config:base` preset that many extend from limits the amount of concurrent branches to 10, but in many cases a limit as low as 3 or 5 can be most efficient for a repository.
The `config:base` preset that many extend from limits the number of concurrent branches to 10, but in many cases a limit as low as 3 or 5 can be most efficient for a repository.
If you want the same limit for both concurrent branches and concurrent PRs, then just set a value for `prConcurrentLimit` and it will be reused for branch calculations too.
However, if you want to allow more concurrent branches than concurrent PRs, you can configure both values (e.g. `branchConcurrentLimit=5` and `prConcurrentLimit=3`).
@ -2560,13 +2560,13 @@ If this setting is true then you would get one PR for webpack@v2 and one for web
If this is set to a non-zero value, _and_ an update contains a release timestamp header, then Renovate will check if the "stability days" have passed.
Note: Renovate will wait for the set amount of `stabilityDays` to pass for each **separate** version.
Note: Renovate will wait for the set number of `stabilityDays` to pass for each **separate** version.
Renovate does not wait until the package has seen no releases for x `stabilityDays`.
`stabilityDays` is not intended to help with slowing down fast releasing project updates.
If you want to slow down PRs for a specific package, setup a custom schedule for that package.
Read [our selective-scheduling help](https://docs.renovatebot.com/noise-reduction/#selective-scheduling) to learn how to set the schedule.
If the amount of days since the release is less than the set `stabilityDays` a "pending" status check is added to the branch.
If the number of days since the release is less than the set `stabilityDays` a "pending" status check is added to the branch.
If enough days have passed then the "pending" status is removed, and a "passing" status check is added.
Some datasources do not provide a release timestamp (in which case this feature is not compatible), and other datasources may provide a release timestamp but it's not supported by Renovate (in which case a feature request needs to be implemented).