gitlab>renovate-bot/renovate-runner on an renovate.json doesn't seem to work with automerge

[nhmarujo]

What would you like help with?

I would like help with my configuration

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

Gitlab
Renovate 37.367.0

Please tell us more about your question or problem

We configured gitlab>renovate-bot/renovate-runner on the extends of config.js and everything seemed to be working as expected. But once we decided to move that to the extends of a renovate.json file sitting just next to it (to avoid running it for all repos), although it still worked (MRs with bumps are open) the automerge stopped taking place.

Any clue why this might be happening? Is it because it is now taking place at a different stage and automerge configured on config.js doesn't cover it?

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[rarkins]

Renovate should include "automerge" in its logs, please get debug logs so we can take a look

[nhmarujo]

I understand - I will try to look further at the logs and see if I can find any snippet there that I can share to shed some light

[rarkins]

Sharing selected logs without leaking information is possible to do and there's thousands of examples in this repo of people from companies doing so

[nhmarujo]

Hi @rarkins I was checking further the logs and I think I found the explanation for the behaviour I was not expecting:

In order to be able to try our changes we went back with the version. So it created again the Merge Request but didn't automerge because it found out there existed already a merged Merge Request with same title.

I assume that behaviour is intentional.

[rarkins]

Yes, if there's an automerge, then a revert (or something else which causes the same update to be raised), then the same PR will have automerge disabled as a intentional precaution to avoid loops of a bad version

[nhmarujo]

Thank you for the clarification @rarkins . I think is perfectly fine as it is, we were just mislead by our own testing. 😄 Thanks for everything, think we can close this one. Have nice weekend!