Ask HN: What makes a good code review?

My team at work is trying to formalize and iterate on our processes, and one process that currently is very much not nailed down is the code/pull request review.

What in your experience makes a good and valuable or bad code review? One that is valuable for the codebase, developer and reviewer?