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
HackRU2013-GH
Search
Sponsored
·
SiteGround - Reliable hosting with speed, security, and support you can count on.
→
Brian Levine
March 28, 2013
Programming
240
4
Share
HackRU2013-GH
Git, GitHub, and workflows.
Brian Levine
March 28, 2013
Other Decks in Programming
See All in Programming
ネイティブアプリとWebフロントエンドのAPI通信ラッパーにおける共通化の勘所
suguruooki
0
230
AI活用のコスパを最大化する方法
ochtum
0
370
車輪の再発明をしよう!PHP で実装して学ぶ、Web サーバーの仕組みと HTTP の正体
h1r0
2
480
「効かない!」依存性注入(DI)を活用したAPI Platformのエラーハンドリング奮闘記
mkmk884
0
290
AI Assistants for YourAngular Solutions @Angular Graz, March 2026
manfredsteyer
PRO
0
140
今からFlash開発できるわけないじゃん、ムリムリ! (※ムリじゃなかった!?)
arkw
0
180
テレメトリーシグナルが導くパフォーマンス最適化 / Performance Optimization Driven by Telemetry Signals
seike460
PRO
2
210
RSAが破られる前に知っておきたい 耐量子計算機暗号(PQC)入門 / Intro to PQC: Preparing for the Post-RSA Era
mackey0225
3
110
Codexに役割を持たせる 他のAIエージェントと組み合わせる実務Tips
o8n
4
1.5k
AIと共にエンジニアとPMの “二刀流”を実現する
naruogram
0
120
Migration to Signals, Signal Forms, Resource API, and NgRx Signal Store @Angular Days 03/2026 Munich
manfredsteyer
PRO
0
220
ポーリング処理廃止によるイベント駆動アーキテクチャへの移行
seitarof
3
1.3k
Featured
See All Featured
How to optimise 3,500 product descriptions for ecommerce in one day using ChatGPT
katarinadahlin
PRO
1
3.5k
Breaking role norms: Why Content Design is so much more than writing copy - Taylor Woolridge
uxyall
0
240
Mozcon NYC 2025: Stop Losing SEO Traffic
samtorres
0
190
Between Models and Reality
mayunak
3
250
Embracing the Ebb and Flow
colly
88
5k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.7k
Building the Perfect Custom Keyboard
takai
2
720
Ten Tips & Tricks for a 🌱 transition
stuffmc
0
95
GraphQLの誤解/rethinking-graphql
sonatard
75
12k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
199
73k
Into the Great Unknown - MozCon
thekraken
40
2.3k
Code Review Best Practice
trishagee
74
20k
Transcript
Git and GitHub Workflows for Fun and Profit
Brian Levine GitHub: @balevine Email:
[email protected]
Twitter: @Brian_A_Levine (but don't
bother)
None
version control is awesome
version control is awesome distributed even more ^ ^
git repository : all your code
git repository : all your code all of its history
git repository : all your code all of its history
all collaborators
git repository : all your code all of its history
all collaborators all the time
commit early commit often “git commit should be used as
often as ctrl+s” - someone I once overheard
branching master
branching master cool-feature
branching and merging master cool-feature
branching and merging real life is messy
remotes https://github.com/balevine/impress.js URL specific
remotes git fetch git merge git pull fetch stuff
remotes git fetch git merge git pull fetch stuff git
push push stuff and
None
remote repositories GitHub gives you
remote repositories interface for git GitHub gives you
remote repositories interface for git forking GitHub gives you
remote repositories interface for git forking merging GitHub gives you
tools for sharing GitHub gives you
ideas / problems and solutions Issues Pull Requests and
bug tracking Issues
bug tracking feature requests Issues
bug tracking feature requests cool ideas Issues
ask someone to merge your changes into their repository or
branch Pull Requests
just what it sounds like Pull Requests
just what it sounds like but more Pull Requests
code review Pull Requests
code discussion Pull Requests
let's talk about workflows
should be intuitive workflows
should be easy workflows
fork a repository Fork and Pull
fork a repository make a pull request Fork and Pull
here's how we roll master is stable
here's how we roll master is stable topic branches for
everything
here's how we roll master is stable topic branches for
everything commit locally
here's how we roll master is stable topic branches for
everything commit locally push often
here's how we roll master is stable topic branches for
everything commit locally push often pull request to discuss
here's how we roll master is stable topic branches for
everything commit locally push often pull request to discuss merge to master when ready
all together now commit early and often
all together now commit early and often use branches wisely
all together now commit early and often use branches wisely
use Issues for bugs and features
all together now commit early and often use branches wisely
use Issues for bugs and features use Pull Requests for code
all together now commit early and often use branches wisely
use Issues for bugs and features use Pull Requests for code find a workflow that's good for you
all together now commit early and often use branches wisely
use Issues for bugs and features use Pull Requests for code find a workflow that's good for you (but we think ours rocks)
there's a whole world of good stuff out there teach.github.com
training.github.com
stalk follow me for more info and fun pictures of
my dogs or email me your questions @Brian_A_Levine
[email protected]