The Art of the Pull Request
summary
Claim: treat pull requests as the basic unit of asynchronous collaboration not just post facto reviews. At Zalando scale—~15,000 employees, ~2,000 engineers across ~200 teams—this reduces coordination overhead. Practical steps: open a PR at planning (empty commit allowed), link to issue for end-to-end motivation, use a PR template that checks CLA, tests and dependencies. Example failures include Habitat PRs with no rationale forcing maintainers to read commits; the template approach surfaces intent and speeds merges.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:00Community in tech orgs
- 3:32Small teams to communities
- 5:22Motivating teams
- 8:59What is a pull request
- 12:13Async communication
- 14:24Good vs bad PRs
- 17:35Structuring meaningful PRs
- 18:36Using pull requests in organizational workflows
- 20:23Pull requests as a tool for alignment
- 21:06Q&A
related talks
28mPull Requests: Merging good practices into your project
11mPull Requests: Merge With Your Team
29mThe Art of Humanizing Pull Requests (PR’s)
29mThe art of humanizing Pull Requests (PR’s)
38mPull Requests and Reviews for Good
30mEffective Pull Request Reviews
21mA Guide to Perfecting Pull Requests
26mThe Art of Humanizing Pull Requests