GitHub Flow — AWS Summit Tokyo 2015

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