github-flow.md

実践 GitHub Flow

• @cobyism
• GitHub
  • 9.7M devs
  • 23.3M projects
  • 293 employees
  • 65% remote
  • 北米と西欧がメイン、アジアも日本中国台湾フィリピンあたり

GitHub Flow

• "Use the simplest possible system that will work for your team" by Scott
• Keep It Simple
• master -> feature branch -> pull request
  • build -> review -> deploy
• approachable, lightweight, scalable
• NOT just for software
  • branch name は purpose
  • support, blog-posts, sales, training...
• company-wide continuous improvement

feature development at GitHub

tiny fix

• typo みたいな tiny fix は quick PR
  • Web 上で作る
• hubot ChatOps deploy
  • locked? n person waiting
  • Deployments API
  • deploy 回数の累積グラフ生成
• merge

middle change

• branch-lab
  • always available
  • 適当なドメインがふられる
• PR -> discuss -> branch deploy

big change

• cut down to small size
• feature flag
  • def new_feature_enabled?
  • 特定のチーム限定で公開
• Devloper Tools
  • 特定の関数が呼ばれた回数のグラフ
• dark shipping
  • realistic load
  • minimal impact
  • allows iteration
• Question も GitHub 上で
  • perfoemance, doc, sec, fallback, dependencies, ...
• post-ship health check
  • 1, 3, 6 months
  • learn from the past

FAQ

• large teams
• too simple to be true?
• if things go wrong?
• trust is hard!
• when to use github flow?

• write good docs
• invest in automation
• build trust
  • focus on trusting software
• discuss early
• question complexity
  • anytime open issue, discuss
• embrace flow