Self-service quality
summary
Claim: treating pull requests as a process turns verification into continuous self-service feedback so teams find bugs earlier and take smaller risky steps. Practical pieces: a one-page contribution guide, opening a draft pull request to run a CI build on merged branch, and enforcing simple checklists for docs vs bug vs refactor. Result is early integration, asynchronous reviews, and the ability to “roll forward” — isolated changes that are reviewed, fixed, and merged, and that work in practice.
AI-written summary · about
chapters (6)
- 0:00Self-service quality intro
- 1:09Open vs enterprise projects
- 4:43Ideas from PRs
- 9:38PR process explained
- 17:49Key lessons from open source
- 19:57Q&A
related talks
53mShift Left Testing for Continuous Collaboration
57mA Meritocracy of Pull Requests
11mTransforming Code Review into a Learning Tool for QA Teams
32mBuilding Confidence Together: Continuous Integration & Testing
10mQuality Assistance vs Quality Assurance
21mHow To Make AI-Assisted OSS Contributions Review-Ready
33mCode review for Open Source
47mCode review beyond code style