GitHub Flow — AWS Summit Tokyo 2015

Ee5bae7fa46b3195869c285ecbb4619e?s=47 Coby Chapple
June 03, 2015
Technology
16
3.7k

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

More Decks by Coby Chapple

See All by Coby Chapple
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
0
59
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
1
150
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
0
150
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
3
200
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
9
1.3k
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
0
24
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
94
29k
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
3
1k
Ee5bae7fa46b3195869c285ecbb4619e?s=48 cobyism
6
930

Other Decks in Technology

See All in Technology
9625fe974bd2b3df38c1f86054fbe04b?s=48 vlayusuke
0
120
B0efb6defa622f75aaaf56e5ee439a59?s=48 firebasethailand
1
110
6f8838b2708a87ccf1015030f16880ef?s=48 godel
0
180
8a84268593355816432ceaf78777d585?s=48 dena_tech
0
900
7f68f5f85f4a39df7d8d3c81cbbfb788?s=48 p1ass
3
680
40661cda330920ea2a854566ae19bbe9?s=48 wyamazak_uhuru
0
340
93fc2d713bc4d0e9c594bf8c9e6bcc62?s=48 oztick139
0
110
8434e5fcdb11033234455d4b2bfb6bb3?s=48 voyage_tech
0
600
E8da8d13d06ca69dbe019ecad71ed2a4?s=48 vinaygaba
2
230
5af8e5bd2f24e4ea0cee732c6cc259b3?s=48 haruharuharuby
0
200
0aa238a274c2397214b20d6eed58939b?s=48 moomooya
0
340
9321a57bcb62d9d6fca07b5c5ca6f6d0?s=48 ohbashunsuke
1
460

Featured

See All Featured
719435d98d452de7ac367c828266cf01?s=48 erikaheidi
11
3.9k
9fa239b3154a0169d99ab7bf1422dd12?s=48 marcelosomers
220
14k
7fa6101cd43067653cf4ac6c7ca54305?s=48 akmur
252
19k
1f74b13f1e5c6c69cb5d7fbaabb1e2cb?s=48 sferik
609
54k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
492
110k
2bb923c57a1fdc3a2eb484bb8d565fd2?s=48 ufuk
55
5.2k
Ae14cc4491ac334f9cd23f9f93b4305e?s=48 orderedlist
PRO
326
35k
95d9f37115fbb0d13135d0f77132f856?s=48 morganepeng
90
13k
0bce06bd06ee7a2c4f5500f25dcf7f18?s=48 paulrobertlloyd
71
3.5k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
266
16k
1519587b1a0febb658c36c94f6272b0d?s=48 roundedbygravity
241
20k
245cee81a9c424266e5e401d844ea881?s=48 lara
169
9.3k

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. ⁉

  11. 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

  12. SIMPLE KEEP IT

  13. FLOW GITHUB

  14. None

  15. "

  16. " #

  17. " $ $ $ # $

  18. " % $ $ $ # $

  19. MASTER FEATURE BRANCH PULL REQUEST

  20. DEPLOY BUILD REVIEW

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

    but GitHub turns it into flow. Chris Wanstrath @defunkt // GitHub Co-founder, CEO

  22. #★ Approachable ★ Lightweight ★ Scalable

  23. NOT JUST FOR SOFTWARE ✨&

  24. github / ! github

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

    / ! github

  26. COMPANY-WIDE CONTINUOUS IMPROVEMENT

  27. KAIZEN վળ

  28. FEATURE DEVELOPMENT AT GITHUB & SHIP IT!

  29. & & &

  30. & & &

  31. & & & New Issue

  32. & & &

  33. & & &

  34. & & &

  35. & & & QUICK PULL REQUEST

  36. & & &

  37. & & &

  38. & & &

  39. & & & HUBOT github / hubot '

  40. & & &

  41. & & &

  42. & & &

  43. & & &

  44. & & & % Merge Pull Request

  45. & & &

  46. & & & ✨)

  47. & & &

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

  49. & & &

  50. & & &

  51. & & &

  52. & & &

  53. & & &

  54. & & &

  55. WHY SO MANY OPTIONS?

  56. & & &

  57. & & & PULL REQUEST DISCUSS BRANCH DEPLOY

  58. & & & $ $ " # %

  59. " % & & & $ $ $ # $

    $ $ -

  60. & & & #⚡ % Merge Pull Request ✨)

  61. & & &

  62. & & & FEATURE FLAGS

  63. & & & def new_feature_enabled? … end

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

    Current functionality end

  65. & & & def new_feature_enabled? preview_features? end

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

  67. & & & def new_feature_enabled? true end

  68. & & & jnunemaker / flipper '

  69. & & &

  70. & & & DARK SHIPPING

  71. & & &

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

    Allows iteration

  73. & & & PRR PRODUCTION READINESS REVIEW

  74. & & & QUESTIONS ★ General ★ Dependencies ★ Fallbacks

    ★ Performance ★ Documentation ★ Security

  75. & & & PSHC POST-SHIP
 HEALTH
 CHECK

  76. & & & PRR PSHC

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

    months ★ 6 months

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

    months ★ 6 months FEEDBACK

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

    months ★ 6 months FEEDBACK

  80. & & & LEARN FROM
 THE PAST.

  81. COMMON QUESTIONS ?

  82. LARGE TEAMS?

  83. TOO SIMPLE TO BE TRUE?

  84. IF THINGS GO WRONG?

  85. WHAT ABOUT CLEAN HISTORY?

  86. TRUST IS HARD!

  87. WHEN TO USE GITHUB FLOW?

  88. TRY IT. PICK WHAT WORKS

  89. IT WORK !MAKING

  90. WRITE
 GOOD DOCS.

  91. INVEST IN
 AUTOMATION.

  92. BUILD
 TRUST.

  93. DISCUSS
 EARLY.

  94. QUESTION COMPLEXITY.

  95. EMBRACE FLOW.

  96. Thank you! cobyism 0 cobyism.com (

  97. None