How Angular manages community contributions and repositories
summary
Explains concrete practices: automatic locking of closed issues after 30+ days using github actions and octokit plus a standard comment — about 60,000 inactive closed issues get locked in three weeks; handling ~120 issues and ~135 PRs per week; shifting builds to remote build execution with remote caching so CI and dev machines share artifacts and unit tests run roughly 33% faster; a caretaker role and an internal app coordinate merges, syncing to Google and releases, with plans to publicize that tooling.
AI-written summary · about
chapters (10)
- 0:00Start
- 2:20The Problem
- 3:24When to lock issues?
- 7:08Seeing the results
- 9:43Scaling horizontally
- 10:24Remote Build Execution
- 11:03Remote Caching
- 12:54Maintaining Quality, Everytime
- 15:49Introducing the caretaker!
- 17:37Where to find impact next
