Should Renovate use enqueuePullRequest
when enabling GitHub native auto-merge?
#31315
Closed
maxbrunet
started this conversation in
Suggest an Idea
Replies: 1 comment 7 replies
-
I'm pretty sure we use these two features together on this repo without problem. As far as I know GitHub automerge adds it to the merge queue |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Tell us more.
I have a repository with 2 rule sets:
When a new update is available, Renovate:
Creates a PR
Enables GitHub's native auto-merge
The PR is not added to the merge queue and never gets merged
Every time Renovate re-runs on the repository, it tries its built-in auto-merge and fails with HTTP 405 Method Not Allowed
I think for this case, Renovate might need to check if merge queue is enabled and use
enqueuePullRequest
explicitly when enabling auto-merge here:renovate/lib/modules/platform/github/index.ts
Lines 1697 to 1700 in 85786a6
I have seen this issue being reported multiple times, but never with a solution, oddly
enqueuePullRequest
has never been mentioned (maybe it's a new option?)Beta Was this translation helpful? Give feedback.
All reactions