renovatebot / config-help

Please use the Discussions feature of https://github.com/renovatebot/renovate instead
https://github.com/renovatebot/renovate/discussions
MIT License
27 stars 16 forks source link

automerge not working, and weird group names #936

Closed vegerot closed 4 years ago

vegerot commented 4 years ago

Which Renovate are you using?

WhiteSource Renovate App

Which platform are you using?

GitLab self-hosted

What would you like to do?

I want to:

This is the config I wrote to do this:

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base"
  ],
  "separateMinorPatch": true,
  "packageRules": [
    {
      "depTypeList": ["devDependencies"],
      "updateTypes": ["patch"],
      "groupName": "devDependencies (patch)",
      "automerge": true
    },
    {
      "depTypeList": ["devDependencies"],
      "updateTypes": ["minor"],
      "groupName": "devDependencies (minor)"
    },
    {
      "depTypeList": ["dependencies"],
      "updateTypes": ["patch"],
      "groupName": "Dependencies (patch)"
    }
  ]
}

This is what the result looks like:

image

viceice commented 4 years ago

remove the update type grom group name, as renovate will autoadd it to pr title

vegerot commented 4 years ago

@viceice will this also make the automerge start working?

viceice commented 4 years ago

you need to check the debug logs for the cause

vegerot commented 4 years ago

Thanks! How can I check the logs in a privately hosted GitLab instance?

viceice commented 4 years ago

in your pr should be a link to the renovate app dashboard

rarkins commented 4 years ago

One of these two answers is incorrect:

image

vegerot commented 4 years ago

@rarkins my apologies. When I click on the user that opened the MR I see image . And when I click on the repo I see

image Which is why I thought we were using WhiteSource Renovate.

rarkins commented 4 years ago

No problem. But in that case you'll need to retrieve the logs from wherever it's run. And I recommend running with LOG_LEVEL=debug in env it --log-level=debug in CLI to capture the debug logs you'll need

vegerot commented 4 years ago

I don't think I have easy access to the logs. In either case, can you see anything wrong with

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base"
  ],
  "separateMinorPatch": true,
  "packageRules": [
    {
      "depTypeList": ["devDependencies"],
      "updateTypes": ["patch"],
      "automerge": true
    },
    {
      "depTypeList": ["devDependencies"],
      "updateTypes": ["minor"],
    },
    {
      "depTypeList": ["dependencies"],
      "updateTypes": ["patch"],
    }
  ]
}

When it comes to the format of the config? If you can't find anything with the auto merge from this, I will have to see about getting those logs.

Thanks!

viceice commented 4 years ago

nope, config seems correct, most of the time automerge is failing because of branch protections

rarkins commented 4 years ago

Can you take a screenshot of the PR details? It will say if it's configured to automerge or not

vegerot commented 4 years ago

It does say it should AutoMerge

image image
viceice commented 4 years ago

Automerge don't work if pr needs approval!

vegerot commented 4 years ago

Oh, thanks! Did not notice that! Is there a way to let Renovate approve itself for patch updates?

viceice commented 4 years ago

nope, you need something else. for github we have an auto-approve-bot

vegerot commented 4 years ago

Thank you!