I agree with both points Tom -- I try to review, approve, and merge code within 15 minutes of the PR coming in.

Then I also require my team to make atomic, semantic commits averaging 10-20 commits per PR to increase velocity when merge conflicts or wrong code inevitability happens.