An unpopular opinion: Get rid of Pull Requests!

on YouTube ↗16m

" summary

Pull requests often balloon, block urgent deploys, and produce “LGTM/Stevie Wonder” approvals that shift responsibility away from authors and reviewers. Advice: ask “is a PR needed?” and only require reviews for new functionality, high‑risk or hard‑to‑reverse changes; for everything else skip or automate. Keep changes tiny (one to two days max), break work into incremental commits behind feature gates, use short-lived branches, and batch trivial repetitive updates with automation rather than manual review.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 0:56Title
3. 1:30Audience participation
4. 4:35Stevie Wonder Approvals
5. 7:30Get rid of Pull Requests
6. 10:20Keep it small
7. 12:48When do we not need pull requests
8. 14:48Conclusion

" related talks

• 29mThe Art of Humanizing Pull Requests (PR’s)Ankita Kulkarni · ScaleConf Colombia 2019
• 28mPull My Code: Effective Code ReviewSimon Gerber · Developer Summit 2020
• 28mPull Requests: Merging good practices into your projectLuca Bezerra · DjangoCon US 2019
• 30mEffective Pull Request ReviewsBas Broek · iOS Conf SG 2022
• 11mPull Requests: Merge With Your TeamEirik Isene · NDC Oslo 2020
• 57mA Meritocracy of Pull RequestsLorna Jane Mitchell · PHP Yorkshire 2019
• 38mPull Requests and Reviews for GoodGregory Farnum · Cephalocon 2024
• 26mThe Art of Humanizing Pull RequestsAnkita Kulkarni · React Boston 2018