The art of humanizing Pull Requests (PR’s)
summary
Covers what pull requests are and practical techniques for creating and reviewing them with empathy, including how to give constructive feedback and respond to reviews. Gives concrete practices for breaking down features, testing strategies, when to take conversations offline, resolving disagreements, and using wording to maintain positive team relationships while delivering high-quality software.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:27THE ART OF HUMANIZING PULL REQUESTS ANKITA KULKARNI, RANGLE.IO
- 1:44WHAT IS A PULL REQUEST (PR)?
- 2:11HOW TO CREATE A PULL REQUEST?
- 2:27BREAKDOWN YOUR STORY/FEATURE AS A USER. I CAN ADD/DELETE ITEMS FROM A LIST
- 6:45TESTS ARE DOCUMENTATION OF YOUR CODE
- 10:15HOW TO CONSTRUCTIVELY REVIEW A PULL REQUEST
- 11:53FEELINGS CAN GET HURT EASILY
- 12:08DON'T BE TOO
- 12:38FAMILIARIZE YOURSELF WITH THE CODE
- 13:31ALWAYS PROVIDE CODE SUGGESTIONS 00
- 18:18MAKE IT AN ES/TS LINT RULE?
- 19:00DON'T LITTER CODE WITH NITPICKS
- 19:39IF YOU THINK FEEDBACK IS VALID, IMPLEMENT IT
- 21:44MAKE YOUR COMMIT MESSAGES OBVIOUS
- 22:30+ INTRODUCING A NEW FEATURE FIXING A BUG ADDING TESTS! PR COMMENTS RELATED
- 23:41WHAT IF THEY ARE REMOTE?
- 24:33DON'T PLAY THE BLAME GAME
- 27:01SMALL THINGS CAN HAVE A BIG IMPACT
- 28:33ANGULAR CONECT
related talks
29mThe Art of Humanizing Pull Requests (PR’s)
30mEffective Pull Request Reviews
26mThe Art of Humanizing Pull Requests
38mPull Requests and Reviews for Good
11mPull Requests: Merge With Your Team
23mThe Art of the Pull Request
28mPull Requests: Merging good practices into your project
21mA Guide to Perfecting Pull Requests