Lock in $30 Savings on PRO—Offer Ends Soon! ⏳
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
HackRU2013-GH
Search
Brian Levine
March 28, 2013
Programming
4
240
HackRU2013-GH
Git, GitHub, and workflows.
Brian Levine
March 28, 2013
Tweet
Share
Other Decks in Programming
See All in Programming
connect-python: convenient protobuf RPC for Python
anuraaga
0
350
CloudNative Days Winter 2025: 一週間で作る低レイヤコンテナランタイム
ternbusty
7
1.9k
Building AI Agents with TypeScript #TSKaigiHokuriku
izumin5210
6
1.2k
Reactive Thinking with Signals and the new Resource API
manfredsteyer
PRO
0
160
無秩序からの脱却 / Emergence from chaos
nrslib
2
12k
テストやOSS開発に役立つSetup PHP Action
matsuo_atsushi
0
140
AIコーディングエージェント(Gemini)
kondai24
0
120
MAP, Jigsaw, Code Golf 振り返り会 by 関東Kaggler会|Jigsaw 15th Solution
hasibirok0
0
210
FluorTracer / RayTracingCamp11
kugimasa
0
180
Integrating WordPress and Symfony
alexandresalome
0
120
Micro Frontendsで築いた 共通基盤と運用の試行錯誤 / Building a Shared Platform with Micro Frontends: Operational Learnings
kyntk
1
1.9k
なあ兄弟、 余白の意味を考えてから UI実装してくれ!
ktcryomm
10
11k
Featured
See All Featured
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.8k
10 Git Anti Patterns You Should be Aware of
lemiorhan
PRO
659
61k
How to Ace a Technical Interview
jacobian
280
24k
Agile that works and the tools we love
rasmusluckow
331
21k
Building a Modern Day E-commerce SEO Strategy
aleyda
45
8.3k
A better future with KSS
kneath
240
18k
Docker and Python
trallard
46
3.7k
Producing Creativity
orderedlist
PRO
348
40k
Optimizing for Happiness
mojombo
379
70k
The Straight Up "How To Draw Better" Workshop
denniskardys
239
140k
BBQ
matthewcrist
89
9.9k
Optimising Largest Contentful Paint
csswizardry
37
3.5k
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]