- master - feat-1 - feat-2 <-- feat-2 is based off of feat-1
I understand that with Change base before delete by champo · Pull Request #1023 · bors-ng/bors-ng · GitHub, bors handles the case where
feat-1 gets merged before
I'm talking about the case where
feat-2 is merged before
feat-1 is. In this case, bors will happily merge
feat-1. I dislike this behavior -- it is never what I want with stacked PRs!
Is there any way to stop bors from performing the merge (ie fail the PR) if the PR's base branch is anything other than the default branch (ie