Secondary renovate config is overwritten by repository config #28613
Unanswered
Cellcote
asked this question in
Request Help
Replies: 1 comment 2 replies
-
You are mixing up the concepts of global/admin config and repo config. When Renovate runs, it first loads global config, including from files. These can include global-only settings. Then Renovate runs on one or more repositories. Each repository can have a config (defaulting to renovate.json) and that config overrides any conflicting global config settings except global-only ones. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
renovatebot/github-action@v40.1.10
Please tell us more about your question or problem
Similar to the solution proposed here (#15490), I want to run a secondary Renovate config on different set of base branches. This secondary config's purpose is to keep past releases up to date with security updates, while the primary config is updating all dependencies.
In the github action workflow, I put this part of the config:
With this, I would assume that it would only use this config and ignore the primary config renovate.json
When I run this, it seems to start with logging the detected config. However, it also detects the repository config (i.e. primary config) and seems to overwrite from there. After that, it seems to have switched base branches, from the one in the secondary config (=>
["/^hotfix/s\\d+/", "/^release/\\d{4}\\.\\d{3}\\.\\d+/"]
), to the one in the primary config (=>main
)How am I supposed to configure this in such a way that it works like I expect?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions