"This PR was configured for branch automerge, however this is not possible so it has been raised as a PR instead."

[janpio]

We are using "automergeType": "branch" but still get a lot of PRs, where I can not figure out why the branch itself was not enough to merge to the main branch. Example: prisma/ecosystem-tests#1452 Is there a way to figure out why automerge did not work?

Logs are probably at https://app.renovatebot.com/dashboard#github/prisma/e2e-tests/304205069, but I could not find anything in there explaining why the automerge did not work only a log of the comment being added.

[viceice]

can you paste the logs here, i think there is a relevant message in the logs, maybe debug only

[rarkins]

If you committed to the main branch after Renovate started running but before it tried to automerge then that would explain the merge failure. Can you compare timestamps to confirm?

[rarkins]

But even if so, we should treat this as a "repository changed" error and not time up on the branch merge altogether

[janpio]

• Renovate log for Job ID 304205069 shows Thursday, February 18th 2021, 6:07:34 pm, not other timestamp unfortunately
• Comment was added: 2021-02-18T17:07:32Z (so Renovate log time is probably when it was written [and not started])
• I manually merged a different Renovate PR a bit earlier: Feb 18, 2021, 6:05 PM GMT+1

Is there a way to see when the Renovate run started?

Update:
From the logs:

DEBUG: latest commit
{
  "latestCommitDate": "2021-02-18T18:05:48+01:00"
}

So it seems that commit had already happened when the Renovate run started.

[rarkins]

This will be fixed by #8796. The problem is that currently we assume that anyone configuring rebaseWhen=conflicted doesn't want us to rebase stale automerging branches.

[janpio]

Nice, that sounds like it should fix it for me. Will continue observing.

[rarkins]

I found a second case where a branch automerge was raised as a PR in this repo. Here's the git merge error:

    "message": "Pushing to https://github.com/prisma/e2e-tests.git\nPOST git-receive-pack (369 bytes)\nremote: error: GH006: Protected branch update failed for refs/heads/dev.        \nremote: error: 4 of 54 required status checks have not succeeded: 1 expected and 3 failing.        \nerror: failed to push some refs to 'https://github.com/prisma/e2e-tests.git'\n",

Code inspection revealed we were (a) fetching only the default 30 per page, and (b) not paginating, so that explains that one. I will fix it today.

[SubJunk]

@rarkins I have another instance of this error, can you help? UniversalMediaServer/UniversalMediaServer#3611 (comment)

[rarkins]

Check your logs