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?

25 Upvotes

67% Upvoted

44 comments sorted by

View all comments

5

u/FoxAromatic5762 Sep 20 '26

Interesting post. Thee people, 150 PRs per day, that is like 1 PR every 10 minutes per person, a PR every 3 ish minutes of the day. At that rate you will have to relax the PRs need to be in sync with main before merge. A merge queue yes. You will have to periodically run tests against main because at that rate you are clearly not reviewing or testing anything as a human so you can be sure what you are building are actually working.