How GitHub Uses GitHub to Build GitHub

on YouTube ↗31m

" summary

Company workflow uses GitHub itself: keep one master and cut simple branches, with master is always deployable and 10–40 deploys a day so rollbacks and tiny changes are safe. Use pull requests as the asynchronous code review and discussion medium — designers and non‑devs join, experiments live there, some features fail but the history helps. Run CI per branch (test suite ~300s), authenticate internal apps via OAuth to avoid reinventing auth, and automate operations with Hubot (≈275 commands) to surface branch/deploy status and daily housekeeping.

AI-written summary · about

" chapters (8)

1. 0:00The struggles of development
2. 3:17Working at GitHub
3. 4:36Asynchronous workflows
4. 8:30Branching and deployment
5. 13:10Power of pull requests
6. 19:55Simplified issue tracking
7. 23:17OAuth for internal tools
8. 26:22Automation with Hubot

" related talks

• 45mHow Github uses GitHub to develop GitHubPeter Murray · DevOps Barcelona Conference 2022
• 45mHow GitHub builds GitHub with GitHubBrian A. Randell, Martin Woodward, Nannette Sperling · Microsoft Build 2023
• 45mHow GitHub builds GitHub on GitHubNeha Batra, Martin Woodward, Taysser Gherfal, Ashley Willis · Microsoft Build 2024
• 42mHow Github (No Longer) WorksZach Holman · RubyConf AU 2013
• 21mGetting the Most Out of GitColin S Gillespie · posit::conf(2023)
• 39mUsing Github for more than codeElizabeth Naramore · SunshinePHP 2014
• 18mShipping at Scale: ChatOps at GitHub #bbuzzGeorgi Knox · Berlin Buzzwords 2016
• 31mBuilding new on top of old: the argument for simplicitySam Lambert · The Lead Developer 2016