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
Git Flow
Search
Sarmad Sangi
September 17, 2014
Technology
0
110
Git Flow
Sarmad Sangi
September 17, 2014
Tweet
Share
More Decks by Sarmad Sangi
See All by Sarmad Sangi
From Backbone.Views To ReactJs
sarmadsangi
1
260
Other Decks in Technology
See All in Technology
あたらしい上流工程の形。 0日導入からはじめるAI駆動PM
kumaiu
5
760
(金融庁共催)第4回金融データ活用チャレンジ勉強会資料
takumimukaiyama
0
140
マーケットプレイス版Oracle WebCenter Content For OCI
oracle4engineer
PRO
5
1.5k
Claude_CodeでSEOを最適化する_AI_Ops_Community_Vol.2__マーケティングx_AIはここまで進化した.pdf
riku_423
2
490
30万人の同時アクセスに耐えたい!新サービスの盤石なリリースを支える負荷試験 / SRE Kaigi 2026
genda
1
420
20260204_Midosuji_Tech
takuyay0ne
1
130
We Built for Predictability; The Workloads Didn’t Care
stahnma
0
130
配列に見る bash と zsh の違い
kazzpapa3
1
110
Kiro IDEのドキュメントを全部読んだので地味だけどちょっと嬉しい機能を紹介する
khmoryz
0
170
Azure Durable Functions で作った NL2SQL Agent の精度向上に取り組んだ話/jat08
thara0402
0
150
インフラエンジニア必見!Kubernetesを用いたクラウドネイティブ設計ポイント大全
daitak
0
330
変化するコーディングエージェントとの現実的な付き合い方 〜Cursor安定択説と、ツールに依存しない「資産」〜
empitsu
4
1.3k
Featured
See All Featured
4 Signs Your Business is Dying
shpigford
187
22k
How to audit for AI Accessibility on your Front & Back End
davetheseo
0
180
Navigating the Design Leadership Dip - Product Design Week Design Leaders+ Conference 2024
apolaine
0
170
A designer walks into a library…
pauljervisheath
210
24k
What the history of the web can teach us about the future of AI
inesmontani
PRO
1
430
Unsuck your backbone
ammeep
671
58k
Dealing with People You Can't Stand - Big Design 2015
cassininazir
367
27k
Reflections from 52 weeks, 52 projects
jeffersonlam
356
21k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.6k
Navigating Weather and Climate Data
rabernat
0
100
Evolution of real-time – Irina Nazarova, EuRuKo, 2024
irinanazarova
9
1.2k
JavaScript: Past, Present, and Future - NDC Porto 2020
reverentgeek
52
5.8k
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.