You open your code review tool on Monday morning to find a PR with 47 changed files — a bug fix, a rename, and a brand new feature all tangled together. Sound familiar? Here's how to write pull requests that reviewers actually want to approve and that deploy with confidence.
What you'll learn:
Chapters: [00:00] The 47-file PR nightmare [01:15] What Makes a PR Atomic [02:45] Keeping PRs Small and Focused [03:01] Split by Layer [03:34] Ship Refactors Separately [03:58] Use Feature Flags [04:21] Atomic Commits Lead to Atomic PRs [05:44] Writing PR Descriptions That Get Approved [06:59] Common Gotchas [07:51] What You Need To Know [08:12] Outro
Links: Our Discord - https://discord.gg/aMTxunVx Buy our shirts - https://store.phparch.com/products/community-corner-podcast-t-shirt
Scott's Social Media: Website - https://scott.keck-warren.com/ Bluesky - https://bsky.app/profile/scottkeckwarren.bsky.social LinkedIn - https://www.linkedin.com/in/scott-keck-warren-91689810/ Mastodon - https://phpc.social/@scottkeckwarren
PHP Architect Social Media:
X: https://x.com/phparch Mastodon: https://phparch.social/@phparch Bluesky: https://bsky.app/profile/phparch.com Discord: https://discord.phparch.com
Subscribe to our magazine: https://www.phparch.com/subscribe/
Thanks to our Partners:
Displace - Infrastructure Management, Simplified https://displace.tech/
PHPScore - Put Your Technical Debt on Autopay https://phpscore.com/
CodeRabbit - Cut code review time & bugs in half instantly with CodeRabbit. https://www.coderabbit.ai/
Honeybadger Honeybadger helps you deploy with confidence https://honeybader.io
Epidemic Sound https://www.epidemicsound.com/
Get PHP Architect Merch at our Store https://store.phparch.com/