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
Brian Levine
March 28, 2013
Programming
4
230
HackRU2013-GH
Git, GitHub, and workflows.
Brian Levine
March 28, 2013
Tweet
Share
Other Decks in Programming
See All in Programming
奥深くて厄介な「改行」と仲良くなる20分
oguemon
1
510
「待たせ上手」なスケルトンスクリーン、 そのUXの裏側
teamlab
PRO
0
490
Updates on MLS on Ruby (and maybe more)
sylph01
1
180
🔨 小さなビルドシステムを作る
momeemt
3
670
Swift Updates - Learn Languages 2025
koher
2
470
Navigation 2 を 3 に移行する(予定)ためにやったこと
yokomii
0
130
Amazon RDS 向けに提供されている MCP Server と仕組みを調べてみた/jawsug-okayama-2025-aurora-mcp
takahashiikki
1
110
AI時代のUIはどこへ行く?
yusukebe
17
8.8k
Android端末で実現するオンデバイスLLM 2025
masayukisuda
1
130
FindyにおけるTakumi活用と脆弱性管理のこれから
rvirus0817
0
490
The Past, Present, and Future of Enterprise Java
ivargrimstad
0
330
rage against annotate_predecessor
junk0612
0
160
Featured
See All Featured
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.1k
Large-scale JavaScript Application Architecture
addyosmani
512
110k
Facilitating Awesome Meetings
lara
55
6.5k
Fireside Chat
paigeccino
39
3.6k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
358
30k
GitHub's CSS Performance
jonrohan
1032
460k
YesSQL, Process and Tooling at Scale
rocio
173
14k
jQuery: Nuts, Bolts and Bling
dougneiner
64
7.9k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
Making Projects Easy
brettharned
117
6.4k
Keith and Marios Guide to Fast Websites
keithpitt
411
22k
Statistics for Hackers
jakevdp
799
220k
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]