Understanding the rationale of forcing dependabot target-branch to default on security updates

[woldie]

Select Topic Area

Question

Body

A good many of us use non-default branches to represent non-prod environments, like QA. We want to be able to test the code in these branches before merging those changes to the default main branch. Test before a release, it just makes horse sense.

Can I understand the rationale behind forcing security updates coming from Dependabot to target the default branch unconditionally? Don't you not want us to test? Why are you trying to jam security updates? And why take this risk of being wrong and pushing a breaking change, do you not have a legal department? Nothing makes sense, the world is broken.

Out of protest, I will delete all dependabot security update pull requests, swatting them away as another example of bureaucratic busywork friction, until you allow us to choose a target-branch for security updates.

Thank you for your time and attention to this matter.