🐛 Bug: Renovate merges PRs with failing migration tests when release flow unlocks branch protections (I think) #1742
Labels
status: accepting prs
Please, send a pull request to resolve this!
type: bug
Something isn't working :(
Bug Report Checklist
main
branch of the repository.Expected
Renovate PRs with failing CI statuses should not be merged into
main
.Actual
Look at all these PRs whose automerges merged with ❌ CI:
In addition to being annoying for me to have to keep reverting the PRs, I think it's also an indication that the current release flow is flawed. Right now the release flow is:
main
branch protections in memorymain
branch protections on GitHubmain
branch protections on GitHub from memoryBetween 2 and 4 is a general opening for squash merging to happen in this repo - and any downstream repo with a similar setup. Not good.
Or at least I think. I'm not 100% sure. But this is my current best theory and strikes me as reasonable.
Additional Info
I suspect the right solution will be, rather than deleting branch protections, to instead change them surgically to allow the running release user. That way they still block apps like Dependabot and Renovate.
In other words:
main
branch protections in memorymain
branch protections on GitHub to exempt the release bot/usermain
branch protections on GitHub from memory💖
The text was updated successfully, but these errors were encountered: