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
190
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
910

Other Decks in Technology

See All in Technology
229b1596ce57cd0935a2bacd410d87a0?s=48 aaaddress1
2
430
3115a782126be714b5f94d24073c957d?s=48 oracle4engineer
0
320
5b47136bedcba2799edf4fcd27ea66d7?s=48 yaegashi
0
320
664b6e8ebe272fcfa5dbd6070eaf3cd4?s=48 wadayusuke
2
670
53850955f15249a1a9dc49df6113e400?s=48 line_developers
0
140
79dcb04101764d7bf66f898dd446838e?s=48 tsukubachallenge
0
280
A38e9ebe0e62fd6753f555c005ea6551?s=48 tarukosu
0
800
945e5c3ef6a52d8d7394b10a99e26277?s=48 guyrleech
0
110
53850955f15249a1a9dc49df6113e400?s=48 line_developers
0
3.1k
Ad22fcf5773b906c08330f4d57242212?s=48 inductor
3
780
A4d1023b1de7890c67a083d14573882d?s=48 ktgrstsh
0
220
18f1e3993e9ead63e7a0f70d9eb996bb?s=48 wkm2
0
130

Featured

See All Featured
7559f6cff1f5efc2d210965febd4d71c?s=48 bermonpainter
340
25k
2bb923c57a1fdc3a2eb484bb8d565fd2?s=48 ufuk
55
5.1k
A415db3ac9e9668acbc1fb36eead84ac?s=48 mthomps
37
2.2k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
775
240k
027d1ebf66cc039a0bd3b55eeadbe75d?s=48 sachag
266
16k
245cee81a9c424266e5e401d844ea881?s=48 lara
168
9.1k
1177e050db6bafe62885362edf6e3537?s=48 lauravandoore
436
28k
44b54d2ffcb7857004071cc6795dde11?s=48 cassininazir
342
20k
8081b26e05bb4354f7d65ffc34cbbd67?s=48 chriscoyier
142
19k
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
163
18k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
308
21k
E837d2996f52008ace055a08fbfff992?s=48 frogandcode
121
20k

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