I review a lot of code and I am worried I am the annoying reviewer. Here is the rule I try to follow:
Block the merge for: correctness bugs, security issues, missing tests for risky logic, API changes that are hard to undo, anything that will confuse the next maintainer.
Comment but do not block (prefix with nit:): naming preferences, small refactors, style differences that a formatter does not handle.
Do not comment at all: anything a tool can decide. If I am typing "please add a trailing newline" in a review, the process is broken, not the author.
Two habits help: say why ("this loop is quadratic if the list grows") instead of "change this", and ask a question when unsure ("is this intentionally nullable?").
What do you do when someone's code is correct but written in a style you dislike?