-
Notifications
You must be signed in to change notification settings - Fork 16
[Question] automerging #184
Comments
Renovate will only merge to the base branches you configure it to, and only to the ones that GitHub permits it to. Don't configure automerge on branches you don't want, and if configure GitHub branch protection if you want to be extra careful.
This is not possible because it's GitHub that enforces this rule, not GitHub. If you mandate PR approvals, then any Renovate PR needs approval. But you can install the companion app Renovate Approve and it will auto-approve any Renovate PR that is set to automerge, so you don't have to.
Same answer as the first point. Renovate won't push/automerge unless you configure it to, and can only do that if you don't protect the branch.
This is a good suggestion, but could not be done via GitHub's interface so would need to be done via the Dashboard. |
I guess you mean
It could be via the Dashboard but |
should such a {
"commitMessagePrefix": "[renovate] ",
"groupName": "all dependencies",
"labels": [
"renovate"
],
"npmToken": "<redacted>",
"packageRules": [
{
"packagePatterns": [
"^@dmx/"
],
"schedule": "at any time",
"automerge": true
},
{
"managers": [
"circleci"
],
"schedule": "at any time",
"automerge": true
}
],
"rangeStrategy": "bump",
"schedule": "before 3am on the first day of the month",
"automerge": false
} expected rules:
|
Yes I think that's right. Beware though that you'll automerge major dependencies too, so I suggest adding a third package rule disabling major automerge using updateTypes. |
unfortunately neither the {
"automerge": true,
"commitMessagePrefix": "[renovate] ",
"groupName": "all dependencies",
"labels": [
"renovate"
],
"major": {
"automerge": false
},
"npmToken": "<redacted>",
"packageRules": [
{
"packagePatterns": [
"^@dmx/"
],
"schedule": "at any time"
},
{
"managers": [
"circleci"
],
"schedule": "at any time"
}
],
"rangeStrategy": "bump",
"schedule": "before 3am on the first day of the month"
} e.g. renovate opened this PR https://github.com/dmx-io/core-microservice/pull/42 and it doesn't merge it though it displays |
The approve bot is only triggered on PR creation and you probably installed it after that PR was created. Please close that PR but try leaving the branch so that it doesn't need to be tested again, you will hopefully see a new PR and this time the bot will approve like this: Then you need to wait for the next run and it should automerge if other tests have passed. |
Now Btw. I have 2 other questions:
|
Renovate runs hourly, so you will need to wait for the next run (or something else that triggers a run).
This is not possible according to GitHub, i.e. a single user or bot always counts as 1. We'd need yet another bot.
Yes, so long as nobody else had to add a commit in order to get it to pass. |
Thanks, renovate finally merged a PR. |
Which Renovate are you using? App
Which platform are you using? GitHub
What is your question?
I would like to configure in this way:
develop
master
Ideally for a given organization the first PR for a given version e.g.
[email protected]
should require an approval and if another PR (in a different repo) has all the versions previously approved, it should be automerged.Here renovatebot/renovate#846 I was proposed to ask a question in
config-help
. I found #152 but it seems to not answer my questions.The text was updated successfully, but these errors were encountered: