Efficient PR reviews are crucial; smaller PRs enable thorough scrutiny, ensuring that issues are identified quickly, enhancing the overall quality of the codebase.
I do not advocate artificial splitting like splitting a PR into two, one containing all the code and another with just the tests, as this approach fails to yield any benefits I share below.
When I refer to small PRs, I mean dividing a larger PR into multiple smaller, logically coherent PRs. Each smaller PR should be standalone, mergeable, and deployable.
Everyone is busy with their own work, and when you ask someone to review a PR, you are essentially requesting their time.
Collection
[
|
...
]