Check out something like Bors, which implements a paradigm that fixes this class of issue: https://github.com/bors-ng/bors-ng
(Homepage: https://bors.tech/)
(Homepage: https://bors.tech/)
Even if you don't have a supper high commit frequency it is still nice to enable certain rebase/stacked PR workflows. Which can remove a lot of friction even for teams which "just" have idk. 6 PRs merged per day (but other PRs which are based on top of this PRs in review and progress maybe stacked multiple layers deep).
OP’s numbers are 120 commits per hour and 5 minute test run, I’m wondering if adopting bors would necessarily reduce that to 12 commits per hour.
https://github.com/bors-ng/bors-ng/blob/master/README.md#how...
Definitely recommended. We run ours on a Heroku instance it’s cheap and almost entirely maintenance free.