Documenting automerge + lockFileMaintenance in Configuration Options

[jamesbraza]

Tell us more.

It looks like from #712, lockFileMaintenance now supports automerge. However, looking at its current docs, this automerge capability is not mentioned anywhere.

Can we add automerge mentions to the lockFileMaintenance somewhere?

[jamesbraza]

Same thing goes for pre-commit, I am wondering if we can have:

{
  "pre-commit": {
    enabled: true,
    automerge: true,
  }
}

Fwiw this seems to pass with https://github.com/renovatebot/pre-commit-hooks

[rarkins]

Automerge works on any PR and is documented independently

[jamesbraza]

I guess I don't follow what you meant by "works on any PR".

So let's say I want to:

• Automerge pre-commit changes
• Not automerge lock file changes

So I don't think a root level automerge can work. Would this be the way to set it up?

{
  $schema: "https://docs.renovatebot.com/renovate-schema.json",
  extends: ["config:recommended"],
  lockFileMaintenance: {
    enabled: true,
  },
  "pre-commit": {
    enabled: true,
    automerge: true,
  },
}

To me, it's unclear the list of sub-key allowable in lockFileMaintenance and pre-commit. In this case, it's unclear if automerge is a valid sub-key of pre-commit

[rarkins]

Keep it simple and configure automerge using packageRules

[jamesbraza]

Please forgive me for re-asking questions, but it's not clear how to configure lockFileMaintenance with packageRules. The default for lockFileMaintenance doesn't mention packageRules at all.

Can you confirm that it would look something like this:

{
  "packageRules": [
    {
      "matchUpdateTypes": ["lockFileMaintenance"],
      "automerge": true,
    }
  ]
}

[jamesbraza]

I found this: https://docs.renovatebot.com/key-concepts/automerge/#automerge-lock-file-maintenance

It documents the answer to my question. It would be good to link this here in lockFileMaintenance