~/talk

How Github uses GitHub to develop GitHub

links:none on file
slides:none on file

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

  1. 0:00Introduction to talk
  2. 1:07How GitHub works philosophy
  3. 6:04Planning work with GitHub
  4. 15:06Building features at GitHub
  5. 18:13Developer friction and CodeSpaces
  6. 23:08Feature flags and experiments
  7. 26:15Pull requests and deployment model
  8. 27:59Security practices at GitHub
  9. 31:27Entitlements and access control
  10. 33:15Automation with Hubot and Heaven
  11. 35:44Merge trains and deployment
  12. 42:10Q&A session
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.