bors r+ work well on multiple PRs (ex.: PR#1 and PR#2) that are ready to be merged around the same time.
But as soon as that staging branch is merged by bors onto master, quickly following up with another bors r+ on another PR(#3) fails. Bors will correctly create a new staging branch and start building it, and builds successfully but the merge is “cancelled” by bors, probably since it is out-of-date with master. So we need to go back to PR#3 issue another bors r+.
I had hoped bors would able to update branch #3 with master, then requeue another bors r+ staging build, that would eventually be merged, without user intervention.
Let me know if this is the expected behavior, or if you have any suggestion so we don’t have to issue multiple bors r+ in that situation. Also, I’ll be happy to open a new thread or use another channel if this isn’t the right place!