The Original intended use is always to enable the person to exclude specific dependencies from remaining added/eliminated/modified when "vendoring" dependencies.
In that situation Renovate initially results in a branch and involved Pull Ask for, after which you can automerges the PR over a subsequent run the moment it detects the PR's status checks are "environmentally friendly".
If you modify branchPrefix, then no Earlier shut PRs will match, which may lead to Renovate recreating PRs in these kinds of situations.
Enabling maintainers to edit pull requests specifically is helpful when Renovate pull requests have to have more adjustments.
Imagine defaultRegistryUrls as a method to specify the "fallback" registries for any datasource, for use when no registryUrls are extracted or configured.
This could switch greater than is intended and will be caught in the course of substitute validation measures, leading to the alternative PR not to be made.
The labels array is non-mergeable, this means if many packageRules match then Renovate uses the last value for labels.
This option controls irrespective of whether Renovate filters new releases depending on configured or detected constraints.
It is really achievable to include this location into the renovate.json file as Portion of the "Configure Renovate" onboarding PR.
Right before development can get started, your contractor will Get hold of your municipal Business office and go over your ideas. They’ll know what permits are required, and they might already have a relationship Along with the municipality, which could enable increase the method.
That deal supervisor makes a different lock file, where all dependency variations are up-to-date to the newest Model.
In the situation that a consumer is routinely included as reviewer (including Renovate Approve bot) and you want to dismiss it for over here the goal of this final decision, increase it for the ignoreReviewers record.
The default benefit for automergeSchedule is "at any time", which capabilities the same as location a null plan.
Enabling this selection will suggest that detected Git submodules are going to be cloned at time of repository clone.