Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Fine Tuning Your GitHub Flow
Search
Stefan Stölzle
October 11, 2017
Technology
140
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Fine Tuning Your GitHub Flow
A Deeper Dive Into GitHub Workflows
@gracepark @stoe
Stefan Stölzle
October 11, 2017
More Decks by Stefan Stölzle
See All by Stefan Stölzle
The Plumbers Guide to the Galaxy
stoe
1
180
Implementing a CI and CD Pipeline with GitHub
stoe
1
170
The 90 Minute App
stoe
2
240
Enterprise Level Web Applications w/ Ext JS 5
stoe
1
150
BYOD 2.0 - Sencha Space
stoe
0
76
SenchaTouch Tizen Showcase + Wearables
stoe
0
170
SenchaTouch Tizen Showcase
stoe
0
160
Build Tizen HTML5 Apps w/ Sencha Architect & Sencha Touch
stoe
1
150
Other Decks in Technology
See All in Technology
世界、断片、モデル。そして理解
ardbeg1958
1
130
壊して学ぶAWS CDK: そのcdk deployで消えるもの、残るもの
k_adachi_01
1
420
Multicaで30個のミニプロジェクトをAIエージェント運用して見えてきたこと
eiei114
0
250
伝票作成AIエージェントを支える、LLMOpsとインフラの選択肢 / AICon2026_takeda
rakus_dev
0
130
AI Native なプロダクト組織の立ち上げ方 : 生産性 100 倍への挑戦
mikesorae
0
200
10年目を迎えた「ABEMA」がどのように AI 活用を推進して、AI 駆動開発にシフトしているのか / How ABEMA, entering its 10th year, is promoting the use of AI and shifting toward AI-driven development
miyukki
0
290
Oracle Exadata Database Service on Cloud@Customer X11M (ExaDB-C@C) サービス概要
oracle4engineer
PRO
2
8.4k
AI Coding Agent時代のcdk-nagガードレール 〜組織ルールを強制CIで守り抜く設計の挑戦〜
mhrtech
3
440
インシデント事例と パッケージの全量解析に学ぶ ソフトウェアサプライチェーンの守り方 / supply-chain-attack-defense
flatt_security
0
140
DMM.com 購入改善推進チーム におけるCodeRabbitを用いた レビューフロー改善の一例
ysknsid25
2
670
「顧客の声を聞かなければ何も始まらない」 ── 顧客の声から生まれた『AI返信補助機能』の開発プロセス / AICon2026_shikata_imai
rakus_dev
0
130
実践!既存 Project への AI-Driven Development 適用〜 一ヶ月で Project 唯一のフロントエンドエンジニアを作り出せ〜
lycorptech_jp
PRO
0
250
Featured
See All Featured
Automating Front-end Workflow
addyosmani
1370
210k
How to Grow Your eCommerce with AI & Automation
katarinadahlin
PRO
1
230
Conquering PDFs: document understanding beyond plain text
inesmontani
PRO
4
2.9k
The State of eCommerce SEO: How to Win in Today's Products SERPs - #SEOweek
aleyda
2
11k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
162
16k
Testing 201, or: Great Expectations
jmmastey
46
8.2k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
38
2.9k
Stop Working from a Prison Cell
hatefulcrawdad
274
21k
How Fast Is Fast Enough? [PerfNow 2025]
tammyeverts
3
660
More Than Pixels: Becoming A User Experience Designer
marktimemedia
3
460
Navigating Weather and Climate Data
rabernat
0
380
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
2.9k
Transcript
Fine Tuning Your GitHub Flow A Deeper Dive Into GitHub
Workflows
stoe
[email protected]
@me_stoe gracepark
[email protected]
Grace Park ! " !
! " Stefan Stölzle
Agenda
Challenges lessons learned from real organizations
A classic vertical organization
From the top down things can be pretty clear, but
from the bottom up it can get foggy real quick
None
Most organizations struggle with awareness of existing enterprise development
None
None
None
Organizational distance between developers directly correlates to bugs and delays
“Good enough” solutions stop gaps, but they don’t fulfill and
retain people
Tools impact Workflow
Git Flow
“a well tested, flexible workflow that works for lots of
developers” Scott Chacon scottchacon.com
Production Staging Testing Dev 1 Dev 2 Dev X
master hotfix release develop feature feature v1.0 v1.1 v2.0
“it’s more complicated than (…) most developers and development teams
actually require” Scott Chacon scottchacon.com
GitHub Flow
master feature
master feature
master develop
master hotfix
master release
one does not simply
merge into master one does not simply
master
master
master
create a feature branch w/ protected master master
master add commits
master add commits
master add commits require CI status
open a PullRequest master
master discuss and review code
master discuss and review code
master discuss and review code enforce code review
master ready to merge
master ready to merge
master ready to merge required branch to be up to
date all status checks passed code review complete
master merge w/ base
master merge w/ base
master merge w/ base restrict who can merge
“It’s too simple. Our teams need more control.” a customer
Your GitHub Flow
develop feature master
hotfix v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0
v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
hotfix v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0
v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
hotfix v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0
v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
hotfix v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0
v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
hotfix v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0
v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
git cherry-pick hotfix v2.9 branch v2.10 branch v2.8 branch v2.11
branch v2.8.0 v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0 v2.9.0
v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 hotfix v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0 v2.9.0
v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 hotfix v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0 v2.9.0
v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 hotfix v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
v2.9 branch v2.10 branch v2.8 branch v2.11 branch v2.8.0 v2.9.0
v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 hotfix v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
git merge v2.9 branch v2.10 branch v2.8 branch v2.11 branch
v2.8.0 v2.9.0 v2.10.0 v2.11.0 v2.8.1 v2.8.2 v2.8.3 v2.9.1 v2.9.2 v2.10.1 hotfix v2.8.4 v2.9.3 v2.10.2 v2.11.1 master
Q&A
Thank you stoe
[email protected]
@me_stoe Stefan Stölzle ! " !
gracepark
[email protected]
Grace Park ! "
None