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
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Stefan Stölzle
October 11, 2017
Technology
140
0
Share
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
170
Implementing a CI and CD Pipeline with GitHub
stoe
1
160
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
74
SenchaTouch Tizen Showcase + Wearables
stoe
0
160
SenchaTouch Tizen Showcase
stoe
0
160
Build Tizen HTML5 Apps w/ Sencha Architect & Sencha Touch
stoe
1
140
Other Decks in Technology
See All in Technology
40代からのアウトプット ― 経験は価値ある学びに変わる / 20260404 Naoki Takahashi
shift_evolve
PRO
5
910
最大のアウトプット術は問題を作ること
ryoaccount
0
320
Oracle AI Databaseデータベース・サービス: BaseDB/ExaDB-Dの可用性
oracle4engineer
PRO
1
170
Kubernetes基盤における開発者体験 とセキュリティの両⽴ / Balancing developer experience and security in a Kubernetes-based environment
chmikata
0
220
仕様通り動くの先へ。Claude Codeで「使える」を検証する
gotalab555
8
3.1k
試されDATA SAPPORO [LT]Claude Codeで「ゆっくりデータ分析」
ishikawa_satoru
0
330
ストライクウィッチーズ2期6話のエイラの行動が許せないのでPjMの観点から何をすべきだったのかを考える
ichimichi
1
310
NgRx SignalStore: The Power of Extensibility
rainerhahnekamp
0
150
あるアーキテクチャ決定と その結果/architecture-decision-and-its-result
hanhan1978
2
560
制約を設計する - 非決定性との境界線 / Designing constraints
soudai
PRO
6
2.4k
推し活エージェント
yuntan_t
1
890
ASTのGitHub CopilotとCopilot CLIの現在地をお話しします/How AST Operates GitHub Copilot and Copilot CLI
aeonpeople
1
210
Featured
See All Featured
ピンチをチャンスに:未来をつくるプロダクトロードマップ #pmconf2020
aki_iinuma
128
55k
Designing Powerful Visuals for Engaging Learning
tmiket
1
330
The Cost Of JavaScript in 2023
addyosmani
55
9.8k
WCS-LA-2024
lcolladotor
0
520
Thoughts on Productivity
jonyablonski
76
5.1k
Fireside Chat
paigeccino
42
3.9k
Applied NLP in the Age of Generative AI
inesmontani
PRO
4
2.2k
AI: The stuff that nobody shows you
jnunemaker
PRO
4
520
We Have a Design System, Now What?
morganepeng
55
8.1k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
37
6.3k
Evolving SEO for Evolving Search Engines
ryanjones
0
170
Large-scale JavaScript Application Architecture
addyosmani
515
110k
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