Speaker Deck
Speaker Deck Pro
Sign in
Sign up
for free
Git Flow
Sarmad Sangi
September 17, 2014
Technology
0
60
Git Flow
Sarmad Sangi
September 17, 2014
Tweet
Share
More Decks by Sarmad Sangi
See All by Sarmad Sangi
sarmadsangi
1
210
Other Decks in Technology
See All in Technology
ocise
0
100
110y
3
690
yuuturn
1
130
caori_t
0
150
kurochan
0
540
yuhta28
1
200
cmwatanabeseigo
0
320
kentaro
1
320
line_developers
PRO
3
470
minamizaki
0
530
tsuyo
0
180
clustervr
0
180
Featured
See All Featured
smashingmag
283
47k
tanoku
86
8.5k
bryan
100
11k
lara
16
2.6k
chriscoyier
499
130k
productmarketing
5
640
mthomps
39
2.3k
deanohume
295
27k
destraynor
146
19k
michaelherold
225
8.4k
pauljervisheath
196
15k
malarkey
119
16k
Transcript
Git Flow
Why are we talking about this ? • We are
growing rapidly geographically • Multiple people per platform • Maintain and Improving code quality • Reduce conflicts
Git Flow • Branching • Pull Requests • Releases •
Merge Masters
Git Flow - Branching
Git Flow - Pull Requests • Helps review code •
Forces us to write good quality code • Shows you if build is failing or has passed (Travis) • Promotes transparency
Git Flow - Releases • Create a Tag for a
release • Release notes
Git Flow - Merge Masters • Responsible for merging Pull
requests • Anyone and everyone can be merge master
How not to screw up ? • Never do git
push - - force
How not to screw up ? • Never do git
push - - force
How not to screw up ? • Avoid committing into
master branch directly even during hot fix.