Add workflow to prevent PR's against stable

[d-torrance]

To hopefully keep us (well, me) from doing things like merging #4287 into the wrong branch again....

Opening this against stable for now to test it out. (Edit: It worked!)

AI Disclosure

Claude wrote pretty much everything

[mahrud]

Wouldn't this fail on #4297?

[d-torrance]

That's targetting development right now, so it's not a problem. (There's a chance I merge it into stable instead, e.g., if something gets merged into development at the last minute that doesn't make it into the release, which happened last time. But I think I usually merge into development first and then just fast-forward stable.)

Plus it doesn't actually prevent merging into stable -- it just serves as a big warning not to. "Oh no! The builds failed! Oh... look at the branch..."

[mahrud]

it just serves as a big warning not to. "Oh no! The builds failed! Oh... look at the branch..."

Unless it was a [ci skip] pull request, such as e4efd1a?

[d-torrance]

D'oh -- yeah lol

[mahrud]

I mean, it's fine as a protection against almost everyone else's PRs, even if it wouldn't have prevented the merge today.

I would be very interested in a merge-bot like the one that homebrew taps use :)