Skip to content
Snippets Groups Projects
Unverified Commit ed4fc35a authored by Oleg Krivtsov's avatar Oleg Krivtsov Committed by GitHub
Browse files

docs(config): document precedence order of config files (#13447)

parent 08bd0840
No related branches found
No related tags found
No related merge requests found
...@@ -10,15 +10,19 @@ Any config you define applies to the whole repository (e.g. if you have a monore ...@@ -10,15 +10,19 @@ Any config you define applies to the whole repository (e.g. if you have a monore
You can store your Renovate configuration file in one of the following locations: You can store your Renovate configuration file in one of the following locations:
- `.github/renovate.json` 1. `renovate.json`
- `.github/renovate.json5` 1. `renovate.json5`
- `.gitlab/renovate.json` 1. `.github/renovate.json`
- `.gitlab/renovate.json5` 1. `.github/renovate.json5`
- `.renovaterc.json` 1. `.gitlab/renovate.json`
- `renovate.json` 1. `.gitlab/renovate.json5`
- `renovate.json5` 1. `.renovaterc`
- `.renovaterc` 1. `.renovaterc.json`
- `package.json` _(within a `"renovate"` section)_ 1. `package.json` _(within a `"renovate"` section)_
_Note_: Storing the Renovate configuration in a `package.json` file is deprecated and support may be removed in the future.
When renovating a repository, Renovate will try to detect the configuration files in the order listed above, and stop after the first one is found.
Renovate always uses the config from the repository's default branch, even if that configuration specifies multiple `baseBranches`. Renovate always uses the config from the repository's default branch, even if that configuration specifies multiple `baseBranches`.
Renovate does not read/override the config from within each base branch if present. Renovate does not read/override the config from within each base branch if present.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment