Automerge: Disabled because a matching MR was automerged previously. #41692
Unanswered
sebhoss
asked this question in
Request Help
Replies: 1 comment
-
|
I'd like to +1 general confusion about the message
that Renovate has started (?) adding to MR descriptions, even on patch and digest updates. I don't understand what it's trying to tell me. Automerge is enabled, was applied before -- so why not do it again? Using grouping, we get the same branch names and MR titles again and again. Is that an issue? Why? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitLab (.com or self-hosted)
Which version of Renovate are you using?
43.55.1
Please tell us more about your question or problem
We are seeing the message in the title in one of our repositories. This seems similar to #22780 but in our case, we are updating from 0.x to 1.x (major update). Our global renovate config does include this:
and the repository configuration looks like this:
{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "customManagers": [ { "customType": "regex", "description": "Update images in .tpl files", "managerFilePatterns": [ "/\\.tpl/" ], "matchStrings": [ "(?<depName>harbor\\.infra\\.run\\/\\S+):(?<currentValue>[^\"\\s]+)" ], "datasourceTemplate": "docker" } ], "packageRules": [ { "groupName": "container-images", "matchDepNames": [ "harbor.infra.run/moodle/*", "harbor.infra.run/infra.run/*", "harbor.infra.run/eventqueue/*" ] } ] }As you can see, we have defined a group here and renovate - so far - was successful in automatically merging MRs. Only after we modified our images to be 1.x, renovate now fails to automatically merge this MR.
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions