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 and Coding Style
Search
Sponsored
·
Your Podcast. Everywhere. Effortlessly.
Share. Educate. Inspire. Entertain. You do you. We'll handle the rest.
→
Bo-Yi Wu
January 24, 2016
Technology
83
0
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
Git Flow and Coding Style
Bo-Yi Wu
January 24, 2016
More Decks by Bo-Yi Wu
See All by Bo-Yi Wu
從觀望到全公司落地:AI Agentic Coding 導入實戰 — 流程整合與安全治理
appleboy
1
710
打造你的 AI 工作流:Agent Skill + MCP 實戰工作坊
appleboy
0
480
從開發到部署全都交給 AI:實作 AI 驅動的自動化流程
appleboy
1
230
AI 不只幫你寫 Code: 當專案從 300 暴增到 1500, 我們如何撐住 DevOps
appleboy
1
340
Agent Skill 是什麼?對軟體產業帶來的變化
appleboy
0
2.8k
用 Claude Code + GitHub Copilot Review 打造 AI 驅動的開發流程
appleboy
0
1.8k
戰略轉變:從建構 AI 代理人到發展可擴展的技能生態系統
appleboy
0
330
The Smart Choice for Command-Line Image Resizing
appleboy
0
63
SSH for GitHub Actions
appleboy
0
320
Other Decks in Technology
See All in Technology
5分でわかる Amazon Connect_20260608
hwangbyeonghun
0
170
Agentic AI 時代のテスト手法: Kiro とはじめるプロパティベーステスト (AWS Summit Japan 2026 | DEV212)
ymhiroki
0
200
フルAIで個人開発して学んだあれこれ / yuruai vol.1
isaoshimizu
0
170
AI時代のエンジニアキャリアについて今一度考える
sakamoto_582
1
970
小さいから、全部わかる。— 常駐AI "xangi" のすすめ
sugupoko
0
250
AWS Summit Japan 2026の振り返りと2027へ向けて / AWS Summit Japan 2026 Recap and Prospects for 2027
kaminashi
1
190
MySQL & MySQL HeatWave Report - June 2026
freshdaz
0
300
AI時代における最適なQA組織の作り方
ymty
3
350
グローバルチームと挑むプロダクト開発
sansantech
PRO
1
150
AIDLC_ヤフーショッピングの取り組み
lycorptech_jp
PRO
0
510
Docker Desktop不要の時代が来る? WSL標準の「wslc」で Linuxコンテナを動かしてみた.
ueponx
0
600
トークン最適化のためのユーザーストーリー分析 / User Story Analysis for Token Optimization
oomatomo
0
160
Featured
See All Featured
Building Better People: How to give real-time feedback that sticks.
wjessup
370
20k
The Illustrated Children's Guide to Kubernetes
chrisshort
51
52k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
55
3.4k
Stewardship and Sustainability of Urban and Community Forests
pwiseman
0
240
[RailsConf 2023] Rails as a piece of cake
palkan
59
6.7k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
49
3.5k
How Fast Is Fast Enough? [PerfNow 2025]
tammyeverts
3
640
The Illustrated Guide to Node.js - THAT Conference 2024
reverentgeek
1
400
Building Flexible Design Systems
yeseniaperezcruz
330
40k
Practical Orchestrator
shlominoach
191
11k
Marketing Yourself as an Engineer | Alaka | Gurzu
gurzu
0
250
Everyday Curiosity
cassininazir
0
250
Transcript
Git Flow and Coding Style Bo-Yi Wu 2015/04/10
Agenda • Git merge vs Git rebase. • JavaScript Coding
Style.
Git merge vs Git rebase
Git merge • Create your branch – $ git checkout –b
‘response’ • Merge from develop branch – $ git merge develop
None
git merge develop
None
New commit Merge branch 'develop' into response (HEAD, response)
None
git merge develop again
None
New commit Merge branch 'develop' into response (HEAD, response)
git checkout develop git merge --no-ff response
None
Git rebase • Create your branch – $ git checkout –b
‘response’ • Merge from master branch – $ git rebase develop
None
Git rebase master
None
No more new commit log
Git rebase master again
None
No more new commit log
Create your new Pull Request git merge --no-ff respnse
None
git rebase vs git merge network graph
None
Rebase vs Merge 優缺點 rebase merge 避免過多 merge
commit log 產生 merge commit log Branch commit log 排到最前面(方便追 蹤) 依照時間排序 commit log network graph 清楚 network graph 不易理解 各別 commit 解決 conflict 一次將全部衝突顯示 可任意修改 commit log 可合併多個 commit (避免過多無意義 commit log)
Rebase vs Merge 使用時機 rebase merge 整理 Branch
commit log 主分支記錄合併 xxxx branch 非主分支開發無需記錄何時合併主分支 主分支請勿使用 rebase 合併任何分支
Develop Note Please rebase master branch and test again before
creating new Pull Request
JavaScript Coding Style Guide
原先架構 https://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml
Google JavaScript Style Guide 無任何範例可參考
Airbnb JavaScript Style Guide https://github.com/airbnb/javascript
Airbnb JavaScript Style Guide 程式碼範例完整 另外也可以參考 ES6 Branch
Yoda Conditions https://en.wikipedia.org/wiki/Yoda_conditions if ($a === ‘1’) { // code
block } if (‘1’ === $a) { // code block } 程式閱讀性高 程式閱讀性低
Yoda Conditions https://en.wikipedia.org/wiki/Yoda_conditions if ($a = ‘1’) { // code
block } 避免此種情況發生
How to prevent the condition? Write Unit Test
Thanks