How to effectively create and review PRs

on YouTube ↗18m

" summary

Advocates keeping PRs as small, focused units—split a feature into endpoint + models, storage/database, and UI PRs so feedback stays short and refactors are limited. Use GitHub features: put a PR template in .github, link issues to auto-close, and embed before/after screenshots or a markdown table for design changes. Reviewers choose between request changes / comment / approve based on crashes, missing tests, or nonblocking questions; authors open draft PRs to self-review, tag designers when needed, and prefix trivial suggestions with "nit."

AI-written summary · about

" chapters (5)

1. 0:00Introduction
2. 1:28PR size importance
3. 7:08PR description tips
4. 13:06Reviewing pull requests
5. 17:21Final thoughts

" related talks

• 29mThe Art of Humanizing Pull Requests (PR’s)Ankita Kulkarni · ScaleConf Colombia 2019
• 21mContinuous Improvements of The Code Review ProcessKeren Kenzi · GeeCON 2024
• 26mThe Art of Humanizing Pull RequestsAnkita Kulkarni · React Boston 2018
• 30mEffective Pull Request ReviewsBas Broek · iOS Conf SG 2022
• 35mLearn how to review PRs like an expertNeil Smith, Matthew Heon, Jan Rodák, Paul Holzinger, Miloslav Trmač · DevConf.CZ 2025
• 39mEffective Code ReviewTahsin Dane · Android Summit 2019
• 22mContinuous Improvements of The Code Review ProcessKeren Kenzi · React Alicante 2024
• 17mGitHub Pull Requests for EveryoneCatherine Meade · JSConf Iceland 2018