How Github uses GitHub to develop GitHub
summary
GitHub runs itself using GitHub issues, projects and a portal called the Hub to track initiatives → epics → batches, with Howie issue templates and slash commands automating labels, boards and RICE scoring. Developers use CodeSpaces 32‑core/64GB prebuilds to eliminate local setup. Releases deploy first via merge trains (then merge only on success), full github.com deployments take ~40–45 minutes, can pause and health‑gate as canaries run. Security uses CodeQL, secret scanning and Flipper feature flags plus Scientist experiments; entitlements and deployment tooling (Hubot, Heaven) are open and auditable.
AI-written summary · about
chapters (12)
- 0:00Introduction to talk
- 1:07How GitHub works philosophy
- 6:04Planning work with GitHub
- 15:06Building features at GitHub
- 18:13Developer friction and CodeSpaces
- 23:08Feature flags and experiments
- 26:15Pull requests and deployment model
- 27:59Security practices at GitHub
- 31:27Entitlements and access control
- 33:15Automation with Hubot and Heaven
- 35:44Merge trains and deployment
- 42:10Q&A session
related talks
01h 06mHow GitHub delivers GitHub using GitHub
31mHow GitHub Uses GitHub to Build GitHub
45mHow GitHub builds GitHub with GitHub
45mHow GitHub builds GitHub on GitHub
18mShipping at Scale: ChatOps at GitHub #bbuzz
48mEnd to End DevOps with GitHub
39mUsing Github for more than code
31mGitHub as a self-sustaining product for large-scale environments
