Why do you perform code reviews? What are your guiding principles for these reviews?
You may want to mention other pages here. Like Engineering Guidelines. To link to another page inline, type @
followed by the name of the page: Engineering Guidelines
Preparation sets your reviewers up for success.
Make sure your commit messages are descriptive.
git commit -m "type (ISSUE) messages"
Your PR descriptions should be an extension of your commit messages. Write about both what the commit changes, and how you implemented the change.
var commentCount = 0;
You might suggest that this be a let
instead of var
.