Azure DevOps: platformAutomerge does not support bypassing branch policies #44473
perpective2410
started this conversation in
Suggest an Idea
Replies: 1 comment
-
|
The PR #33626 was closed due to inactivity, you can create a new PR. It's welcome |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Tell us more.
Description
On the Azure DevOps platform,
platformAutomergeonly calls the plain "Set auto-complete" API - it never sends Azure DevOps' separatebypass-policyflag. This means a PR configured withautomerge: true+platformAutomerge: truestill waits for required branch policies (e.g. minimum reviewers, required builds) to genuinely pass before completing, rather than actually bypassing them.An earlier PR to add this (#33626) was closed unmerged.
Impact
Without native support, self-hosted users who want Renovate to bypass branch policies for trusted, low-risk updates (e.g. digest-only base image pins) have to build their own out-of-band automation that calls
az repos pr update --bypass-policy truedirectly against the Azure DevOps REST API for PRs Renovate has already flagged viaautoCompleteSetBy. This duplicates logic thatplatformAutomergeshould be able to handle on its own, and has to be kept in sync withpackageRulesautomerge eligibility separately.Ask
Could this be reconsidered, either by reviving #33626 or via a new
platformAutomerge-scoped option (e.g.platformAutomergeBypassPolicyor similar) that opts in to sending the bypass-policy flag on Azure DevOps? Happy to provide more context on the workaround we're currently running if useful.Beta Was this translation helpful? Give feedback.
All reactions