I'm having an issue with a junior developer bikeshedding PRs. They are the primary approver for one repository. Things that should be up for an hour or minutes on PR spend days sometimes with back-and-forth comments.
An example from yesterday: I added an artifact to our build system. One line change. Get three back-and-forth comments asking why another thing is there. This is something that has existed for two months and is unrelated to my code change.
The other common set is needing to guide them down the path of a non-initial solution. You know how it is. There is problem Alpha. Initial thought is Solution A. Deeper thinking reveals it won't work because of Problem Zeta. So Solution B is needed. Put up a PR for Solution B, detail why it is implemented that way. First comment, "why not Solution A?" Have to guide them through the rabbit hole of how Solution A can't work because of Problem Z. They realize that and agree.
Socially, the junior developer is friendly and we get along wonderfully. But this blocking behaviour is impeding a lot of work (I've had three weeks of PRs backlog'd waiting for other PRs to get in).
When I asked him to please stop bikeshedding PRs, he started bikeshedding the definition of bikeshedding.