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
github-flow
Search
David Celis
August 15, 2012
Programming
16
930
github-flow
Introduce GitHub to a common git workflow by forking and using pull requests.
David Celis
August 15, 2012
Tweet
Share
More Decks by David Celis
See All by David Celis
From REST to GraphQL: Why a query language is perfect for writing APIs
davidcelis
0
150
Rails Is Enterprise So You Might Internationalise* Your App
davidcelis
0
42
Rails Inflections
davidcelis
5
250
Better Git Commit Messages
davidcelis
8
2.5k
Other Decks in Programming
See All in Programming
CSC307 Lecture 05
javiergs
PRO
0
500
OCaml 5でモダンな並列プログラミングを Enjoyしよう!
haochenx
0
140
メルカリのリーダビリティチームが取り組む、AI時代のスケーラブルな品質文化
cloverrose
2
510
Data-Centric Kaggle
isax1015
2
770
Oxlintはいいぞ
yug1224
5
1.3k
QAフローを最適化し、品質水準を満たしながらリリースまでの期間を最短化する #RSGT2026
shibayu36
2
4.3k
Rust 製のコードエディタ “Zed” を使ってみた
nearme_tech
PRO
0
150
AIフル活用時代だからこそ学んでおきたい働き方の心得
shinoyu
0
130
AI時代のキャリアプラン「技術の引力」からの脱出と「問い」へのいざない / tech-gravity
minodriven
20
6.9k
AI によるインシデント初動調査の自動化を行う AI インシデントコマンダーを作った話
azukiazusa1
1
700
疑似コードによるプロンプト記述、どのくらい正確に実行される?
kokuyouwind
0
380
AIエージェントのキホンから学ぶ「エージェンティックコーディング」実践入門
masahiro_nishimi
5
340
Featured
See All Featured
Practical Orchestrator
shlominoach
191
11k
We Analyzed 250 Million AI Search Results: Here's What I Found
joshbly
1
690
エンジニアに許された特別な時間の終わり
watany
106
230k
Getting science done with accelerated Python computing platforms
jacobtomlinson
2
110
Why You Should Never Use an ORM
jnunemaker
PRO
61
9.7k
RailsConf 2023
tenderlove
30
1.3k
GraphQLの誤解/rethinking-graphql
sonatard
74
11k
How to build a perfect <img>
jonoalderson
1
4.9k
The Language of Interfaces
destraynor
162
26k
sira's awesome portfolio website redesign presentation
elsirapls
0
140
Statistics for Hackers
jakevdp
799
230k
Imperfection Machines: The Place of Print at Facebook
scottboms
269
14k
Transcript
git-flow Wednesday, August 15, 12
git-flow Wednesday, August 15, 12
Typical process Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Seems LEGIT Wednesday, August 15, 12
But there are PROBLEMS Wednesday, August 15, 12
Pushing DIRECTLY MASTER to Wednesday, August 15, 12
NO enforceable CODE REVIEW Wednesday, August 15, 12
People don’t clean up! Wednesday, August 15, 12
How can we do BETTER? Wednesday, August 15, 12
git-flow Wednesday, August 15, 12
github-flow Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Know EXACTLY what you’re MERGING Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
DIFF STATS Wednesday, August 15, 12
Wednesday, August 15, 12
CODE REVIEW Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
Wednesday, August 15, 12
But WHAT about all of those FEATURE BRANCHES Wednesday, August
15, 12
github-flow Wednesday, August 15, 12
github-flow Wednesday, August 15, 12
FORKING Wednesday, August 15, 12
CLONE YOUR FORK Wednesday, August 15, 12
CLONE YOUR FORK Wednesday, August 15, 12
KEEP UP TO DATE Wednesday, August 15, 12
KEEP UP TO DATE Wednesday, August 15, 12
KEEP UP TO DATE Wednesday, August 15, 12
KEEP UP TO DATE Wednesday, August 15, 12
PAIR FORKING Wednesday, August 15, 12
Fetch only what YOU care about Wednesday, August 15, 12
Maintain your repository the way YOU want. It’s YOURS Wednesday,
August 15, 12
Learn how to use git like a PRO Wednesday, August
15, 12
Now you can PRUNE all of those FEATURE BRANCHES *
from the main repository! (once your other team members have forked too) Wednesday, August 15, 12
@davidcelis Wednesday, August 15, 12