The Art of Humanizing Pull Requests (PR’s)
summary
Advocates breaking large changes into small, reviewable commits and break features into small PRs so reviewers get frequent feedback; use inline comments, attach GIFs or screenshots (uses a screen-capture tool) to prove behavior, and add tests that serve as documentation — write tests as documentation. Implement valid suggestions promptly, ask clarifying questions when needed, prefer friendly phrasing and emojis, turn repeated nitpicks into lint rules, and avoid massive PRs (example: a 300‑file change that forced 3‑hour reviews and near‑blind approvals).
AI-written summary · about
chapters (10)
- 0:00Start
- 1:06HI I'M ANKITA
- 2:21BREAKDOWN YOUR STORY/FEATURE
- 4:36IN-LINE WITH THE PROGRAMMER'S OATH
- 5:20ADD COMMENTS ON YOUR PR
- 6:13+SCREENSHOTS/GIFS
- 8:46WHILE WRITING TESTS
- 15:09REWORDING FEEDBACK...
- 16:10USE EMOJIS
- 20:50EXAMPLES...
related talks
26mThe Art of Humanizing Pull Requests
29mThe art of humanizing Pull Requests (PR’s)
30mEffective Pull Request Reviews
21mA Guide to Perfecting Pull Requests
16mAn unpopular opinion: Get rid of Pull Requests!
18mHow to effectively create and review PRs
21mContinuous Improvements of The Code Review Process
38mPull Requests and Reviews for Good