config rule not being applied when baseBranches
is set with multiple branches
#30604
Unanswered
timja
asked this question in
Request Help
Replies: 1 comment 6 replies
-
I think |
Beta Was this translation helpful? Give feedback.
6 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?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
Config rule is:
No
baseBranches
config and it works as expected:https://github.com/timja-org/jenkins-renovate-master-only/blob/d370769fd6a077e2c039579e339868755f5c5799/.github/renovate.json
https://developer.mend.io/github/timja-org/jenkins-renovate-master-only
(unrelated warning is there, that is being sorted by removing the dep in a separate PR)
baseBranches
configured for master and stable-2.462:https://github.com/timja-org/jenkins/blob/4b22341184899a297ba2f9cc0ff70d73c570987b/.github/renovate.json
warning for both dependencies:
difference is these are removed:
Note: I've also seen other weird behaviour with
baseBranches
wildcards and regexes in matchPackageNames didn't seem to work, I had to expand a couple of rules to a full package match (e.g. the springframework rule)Logs (if relevant)
Logs from no baseBranches
Logs from baseBranches version
Beta Was this translation helpful? Give feedback.
All reactions