Smaller pull requests are personally more enjoyable to review because I can quickly develop an understanding of what has changed in a codebase, why it has changed, and if it is correct. When I can, I like to run those changes locally on my machine and play around to solidify my understanding of the changes so that I can ensure that I am reviewing and making comments or approvals with the correct assumptions about the code. I think this process of reviewing is a lot easier to do with smaller pull requests.
In regards to incentivizing teammates to open frequent and small pull requests, I think a good approach would be to provide some guideline for PRs and include why smaller pull requests are preferred. I think most, if not all, engineers would be receptive to logical arguments!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Smaller pull requests are personally more enjoyable to review because I can quickly develop an understanding of what has changed in a codebase, why it has changed, and if it is correct. When I can, I like to run those changes locally on my machine and play around to solidify my understanding of the changes so that I can ensure that I am reviewing and making comments or approvals with the correct assumptions about the code. I think this process of reviewing is a lot easier to do with smaller pull requests.
In regards to incentivizing teammates to open frequent and small pull requests, I think a good approach would be to provide some guideline for PRs and include why smaller pull requests are preferred. I think most, if not all, engineers would be receptive to logical arguments!