NuGroom automatically detects and respects Renovate configuration files in scanned repositories. This allows teams already using Renovate to maintain a single source of truth for dependency management rules.
The following file paths are checked in priority order:
/renovate.json/.renovaterc/.renovaterc.json/.github/renovate.jsonThe first file found is used. If no Renovate config exists, the repository is processed normally.
To disable Renovate detection entirely, use --ignore-renovate on the CLI or "IgnoreRenovate": true in the config file.
| Renovate Field | Effect |
|---|---|
ignoreDeps |
Listed packages are excluded from scanning and update plans for this repository |
packageRules[].matchPackageNames + enabled: false |
Matched packages are excluded from scanning and update plans |
reviewers |
Overrides the tool’s RequiredReviewers for PRs created against this repository |
packageRules[].matchPackageNames + reviewers |
Stored per-package for future use |
renovate.json{
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"ignoreDeps": [
"Newtonsoft.Json",
"Castle.Core"
],
"reviewers": [
"lead@company.com",
"security@company.com"
],
"packageRules": [
{
"matchPackageNames": ["Serilog", "Serilog.Sinks.Console"],
"enabled": false
}
]
}
With this configuration:
Newtonsoft.Json and Castle.Core are completely excluded from the scanSerilog and Serilog.Sinks.Console are excluded from the scanlead@company.com and security@company.com as required reviewers instead of the tool’s configured reviewersRequiredReviewers for that repository. OptionalReviewers from the tool config are still added.When a Renovate config is detected, the scan log shows:
[1/50] Scanning repository: MyRepository
Renovate config found (2 ignored, 2 disabled)
See also: Automated Updates · Configuration