When you refactor a commonly used structure, it's easily possible to hit situations that you described. In those cases, having nicely organized commits are supe

When you refactor a commonly used structure, it's easily possible to hit situations that you described. In those cases, having nicely organized commits are super important. You need to make sure that the commit that does the refactor only does the refactoring. Nothing else, then you can review the PR commit by commit and it becomes much more manageable. When people start doing multiple things in a single commit with 1000's of changes, it does become mentally exhausting to review. Unfortunately, it requires either being extremely diligent when making the commits or being familiar with git rebase -i. Of course, sometimes it's just thousands of lines of new code and impossible to review :).