Pull Requests: Not Just For Code Anymore
summary
Company policy and process docs move into a git repo and are edited via pull requests using GitHub Enterprise and published with GitHub Pages. New Relic records 214 PRs to the processes repo from 48 people in 13 months and 137 architecture PRs from 32 contributors in five months, with single-PR comment threads up to 129 comments. The workflow produces versioned agent specs, forces explicit rationales, surfaces reviewers, reduces surprise changes, and actually works while requiring merge owners and entropy fighters.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:52Dunbar's number
- 5:23explicit implicit
- 6:07accountability!
- 7:08corporate stuff
- 13:37lessons learned
related talks
17mGitHub Pull Requests for Everyone
28mPull Requests: Merging good practices into your project
38mPull Requests and Reviews for Good
23mThe Art of the Pull Request
21mWhat does moving to Pull Requests look like? The nginx story
32mLove and Hate for Pull Requests
21mA Guide to Perfecting Pull Requests
11mPull Requests: Merge With Your Team