GitHub Flow — AWS Summit Tokyo 2015

GitHub Flow — AWS Summit Tokyo 2015

Here are the slides for the presentation on GitHub Flow I gave at AWS Summit Tokyo in June, 2015.

Ee5bae7fa46b3195869c285ecbb4619e?s=128

Coby Chapple

June 03, 2015
Tweet

Transcript

  1. None
  2. cobyism

  3. None
  4. 5,000,000 10,000,000 15,000,000 20,000,000 25,000,000 2008 2009 2010 2011 2012

    2013 2014 2015 (YTD) DEVELOPERS ARE COLLABORATING ON PROJECTS ON GITHUB RIGHT NOW 9.7 MILLION 23.3 MILLION
  5. 293 Employees 65% Remote !

  6. None
  7. COMPANY PRODUCT WORKFLOW VALUES

  8. None
  9. None
  10. Use the simplest possible system that will work for your

    team. Scott Chacon @schacon // GitHub Co-founder http://scottchacon.com/2011/08/31/github-flow.html
  11. SIMPLE KEEP IT

  12. FLOW GITHUB

  13. None
  14. "

  15. " #

  16. " $ $ $ # $

  17. " % $ $ $ # $

  18. MASTER FEATURE BRANCH PULL REQUEST

  19. DEPLOY BUILD REVIEW

  20. Build, review, deploy. All good development goes through these phases,

    but GitHub turns it into flow. Chris Wanstrath @defunkt // GitHub Co-founder, CEO
  21. #★ Approachable ★ Lightweight ★ Scalable

  22. NOT JUST FOR SOFTWARE ✨&

  23. github / ! github

  24. github support blog-posts product docs github sales projects training community

    / ! github
  25. COMPANY-WIDE CONTINUOUS IMPROVEMENT

  26. KAIZEN վળ

  27. FEATURE DEVELOPMENT AT GITHUB & SHIP IT!

  28. & & &

  29. & & &

  30. & & & New Issue

  31. & & &

  32. & & &

  33. & & &

  34. & & & QUICK PULL REQUEST

  35. & & &

  36. & & &

  37. & & &

  38. & & & HUBOT github / hubot '

  39. & & &

  40. & & &

  41. & & &

  42. & & &

  43. & & & % Merge Pull Request

  44. & & &

  45. & & & ✨)

  46. & & &

  47. & & & MASTER FEATURE BRANCH PULL REQUEST LOCAL
 DEVELOPMENT

  48. & & &

  49. & & &

  50. & & &

  51. & & &

  52. & & &

  53. & & &

  54. WHY SO MANY OPTIONS?

  55. & & &

  56. & & & PULL REQUEST DISCUSS BRANCH DEPLOY

  57. & & & $ $ " # %

  58. " % & & & $ $ $ # $

    $ $ -
  59. & & & #⚡ % Merge Pull Request ✨)

  60. & & &

  61. & & & FEATURE FLAGS

  62. & & & def new_feature_enabled? … end

  63. & & & if new_feature_enabled? // New functionality else //

    Current functionality end
  64. & & & def new_feature_enabled? preview_features? end

  65. & & & def new_feature_enabled? preview_features? && team_access?(:some_team) end

  66. & & & def new_feature_enabled? true end

  67. & & & jnunemaker / flipper '

  68. & & &

  69. & & & DARK SHIPPING

  70. & & &

  71. & & & #★ Realistic load ★ Minimal impact ★

    Allows iteration
  72. & & & PRR PRODUCTION READINESS REVIEW

  73. & & & QUESTIONS ★ General ★ Dependencies ★ Fallbacks

    ★ Performance ★ Documentation ★ Security
  74. & & & PSHC POST-SHIP
 HEALTH
 CHECK

  75. & & & PRR PSHC

  76. & & & PRR PSHC ★ 1 month ★ 3

    months ★ 6 months
  77. & & & PRR PSHC ★ 1 month ★ 3

    months ★ 6 months FEEDBACK
  78. & & & PRR PSHC ★ 1 month ★ 3

    months ★ 6 months FEEDBACK
  79. & & & LEARN FROM
 THE PAST.

  80. COMMON QUESTIONS ?

  81. LARGE TEAMS?

  82. TOO SIMPLE TO BE TRUE?

  83. IF THINGS GO WRONG?

  84. WHAT ABOUT CLEAN HISTORY?

  85. TRUST IS HARD!

  86. WHEN TO USE GITHUB FLOW?

  87. TRY IT. PICK WHAT WORKS

  88. IT WORK !MAKING

  89. WRITE
 GOOD DOCS.

  90. INVEST IN
 AUTOMATION.

  91. BUILD
 TRUST.

  92. DISCUSS
 EARLY.

  93. QUESTION COMPLEXITY.

  94. EMBRACE FLOW.

  95. Thank you! cobyism 0 cobyism.com (

  96. None