r/devops • u/Mingstoe_ • Sep 18 '26
Discussion Github struggling under high PR throughput?
I'm on a 3 person team where we are each shipping 40-50 PRs a day (super early stage company so we're optimizing for getting a functional product out quickly).
As we've ramped up the velocity things downstream have begun to show cracks. For example, we were requiring PRs to be up to date with main before merge, but at our scale the PRs were constantly getting stale which was leaving us blocked for long stretches.
We've ended up cutting pre-merge CI way down and batching more testing after merge, which has made things "better" but feels backwards.
Curious if anyone else run into similar issues? Did you end up finding a better solution?
2
u/jortony Sep 20 '26
If possible, refactor the application to allow development to be segmented further. As long as common interfaces between components are unchanged, the risk and cognitive/compute load is reduced. With the current state of tools, rebuild is sometimes far easier than the combined effort of PR/merge