- PR_LINK
this might be the "What problem are you solving" section of a PR
this might be the "How did you solve it" section of a PR
- good reviews ask open-ended questions instead of making strong or opinionated statements.
- offer workarounds that might work better for the situation without insisting those are the only way to proceed
- Additional PR reviewing notes: https://gist.github.com/brianzhou13/f1fff4f72f1f93abd25ec2000f553f36
If you can't understand the code, stop the review and leave a comment. It's likely that there are other engineers who would get stumped by it. Ensure that the code that is being introduced is maintainable
Are there any classes/functions that are hard too read? If so, suggest they should be refactored
Interesting equity-related/like notes
Don't accept PRs that degrade the health of the codebase
points of praise