Stop Using Pull Requests
In a provocative article on Substack, the author challenges the widespread use of pull requests (PRs) in software development, calling them a bottleneck that slows down teams. The piece suggests that PRs create artificial delays, encourage large batches of changes, and lead to context switching for reviewers. Instead, the author proposes a workflow where developers commit directly to the main branch, relying on automated testing, feature flags, and post-commit code reviews to maintain quality. The article cites examples from high-performing teams like those at Netflix and GitHub, which have moved away from PRs in certain contexts. However, the author acknowledges that this approach is not suitable for all teams, especially those with junior developers or in regulated industries. The post has sparked debate in the comments, with some agreeing that PRs can be overused, while others defend them as essential for collaboration and code quality. The article does not provide specific data or case studies, but rather presents a philosophical argument for reducing process overhead.
Challenges a core workflow, potentially reshaping team collaboration and deployment speed.