Tag code-review


I've written about this before in https://www.jvt.me/posts/2019/01/12/self-code-review/ and hugely recommend it - especially when there's a way to mark it as a Draft so it's clear it's not yet ready for review. After you've added comments, it may need you to address things before it can then go out to others in the team

Quoted a post on Twitter
Post details


Liked a post on Twitter
Post details


Bookmarked Conventional Comments by Paul Slaughter 
Post details
Comments that are easy to grok and grep

We've been using emoji for this in the past, which works well as long as everyone remembers what the emoji reflect - I often forget - but doing it this way makes a lot of sense, and having them to be machine-parseable is a benefit!


We've found it to work quite well on my team, as it allows folks to see things they're not necessarily involved in, and actively seeks out their thoughts, as well as not leaving it up to the PR raiser to decide who

(Although we're currently using the "round Robin" approach)

It also doesn't mean others can't review