[solved] Automerge does not work

[jokay]

When I use this configuration the automerge does not work, the user which executes renovate (the pipeline) has all necessary permissions.

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base",
    "docker:enableMajor"
  ],
  "labels": [
    "dependencies"
  ],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0,
  "automerge": true,
  "requiredStatusChecks": null
}

tried this as well without success

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": [
    "config:base",
    "docker:enableMajor"
  ],
  "packageRules": [
    {
      "matchUpdateTypes": [
        "major",
        "minor",
        "patch",
        "pin",
        "digest"
      ],
      "automerge": true,
      "requiredStatusChecks": null
    }
  ],
  "labels": [
    "dependencies"
  ],
  "prHourlyLimit": 0,
  "prConcurrentLimit": 0
}

any help would be much appreciated.

[rarkins]

Describe what you mean by "does not work"?

[viceice]

yes.

[viceice]

BTW: It's a very bad idea to combine "requiredStatusChecks": null with automerge=true. You can get a broken baseBranch!

[jokay]

Ok, on a subsequent run it just closes the merge request.

INFO: PR automerged (repository=renovate/renovate, branch=renovate/docker-renovate-renovate-24.x)
       "pr": 14,
       "prTitle": "Update renovate/renovate Docker tag to v24.89.1"

The changes were not merged into main

This project requires squashing commits when merge requests are accepted. Try again.

Is there any way to support squashing commits ?

[jokay]

BTW: It's a very bad idea to combine "requiredStatusChecks": null with automerge=true. You can get a broken baseBranch!

Yes, if this needs to be run twice anyway, I can keep the checks. This automerge is only enabled for the renovate repo :)

[jokay]

Ok, there exists already issue #7859 for it.