One core issue is that PRs are often too large. I don't believe there are 300 comments on a small PR unless the team is dysfunctional.
Aim to make them as atomic as possible. If it involves adding a significant feature that requires substantial changes to other modules, create a separate branch for it. Within this branch, break the work down into a series of smaller PRs.
When PRs are too large, the process usually suffers from insufficient reviews, excessive nitpicking, or (most often) a combination of both.
Aim to make them as atomic as possible. If it involves adding a significant feature that requires substantial changes to other modules, create a separate branch for it. Within this branch, break the work down into a series of smaller PRs.
When PRs are too large, the process usually suffers from insufficient reviews, excessive nitpicking, or (most often) a combination of both.