The PR that's actually a meeting
Some pull requests are code. Others are organizational disputes written in TypeScript. Knowing which is which saves whole afternoons.
A pull request hits 47 comments. Three reviewers are arguing about something that isn't quite the code. By comment 30 it's clear: this isn't a code review anymore. It's an org chart dispute conducted through diffs.
Spot it early
When the conversation keeps drifting from the change to who owns the area, what we promised in the planning meeting, or whether this is really product's call — you've left review territory. Closing the PR and opening a Slack thread (or a meeting) is faster than another twelve nits.
Pull the conversation up
Code reviews are the wrong altitude for org decisions. They reward terseness and pattern-matching, not nuance. Move it up: 30 minutes synchronously, with the right people in the room, will resolve what 47 comments won't.
If your PR comments would make a better meeting, schedule the meeting.