The life of an Angular pull request
summary
Angular treats a pull request as the unit of change and shows concrete process work: a new StackBlitz template for minimal reproductions, automated triage by a Probot GitHub robot, CI checks via CircleCI and Travis CI, and a Google validation step that tests PRs against real apps. The project reports ~19,000 PRs, ~30,000 closed issues and runs twice‑weekly triage sessions, computes size deltas, and measures throughput so changes actually make it into releases.
AI-written summary · about
chapters (5)
- 0:00Introduction and vision
- 3:57Managing issue reporting
- 10:42Contributing to the project
- 13:58Pull request workflow
- 17:04Sprint planning and closure
related talks
36mTough Decisions: the complexities of maintaining a popular open source project
25mSpace-Age GitOps: The Rise of the Humble Pull Request
46mBuilding Developer Community One Pull Request at a Time
21mWhat does moving to Pull Requests look like? The nginx story
26mA State of Continuous Merge: The Secret to More Productive Dev Teams
27mThe PR Is the UI: Simplifying Argo for Developers
32mAngular as strategy for collaboration and scale
33mWorking backwards