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
200
HackRU2013-GH
Git, GitHub, and workflows.
Brian Levine
March 28, 2013
Tweet
Share
Other Decks in Programming
See All in Programming
Trial
cairolibrary720
1
130
データカタログ運用物語 〜令和6年夏の理想と現実〜
kuro_kurorrr
0
110
生成AIをkintoneに連携してみた
hideg
0
230
3 Effective Rules for Success with Signals in Angular
manfredsteyer
PRO
0
120
Javaの現状2024夏 / Java current status 2024 summer
kishida
4
1.4k
12年前の『型システム入門』翻訳の思い出話
mame
11
1.2k
はしめてのプログラミングとロボット制御
watawatavoltage
0
290
I/O Extended Android in Korea 2024 ~ Whats new in Android development tools
pluu
0
250
CSC307 Lecture 12
javiergs
PRO
0
220
開発部に不満を持っていたCSがエンジニアにジョブチェンしてわかった「勝手に諦めない」ことの大切さ
sakuraikotone
28
16k
「2024年版 Kotlin サーバーサイドプログラミング実践開発」の補講 〜O/Rマッパー編〜
n_takehata
2
260
From Spring Boot 2 to Spring Boot 3 with Java 22 and Jakarta EE
ivargrimstad
0
1.9k
Featured
See All Featured
Git: the NoSQL Database
bkeepers
PRO
423
64k
Web development in the modern age
philhawksworth
203
10k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
13
430
Building Adaptive Systems
keathley
34
2k
GraphQLとの向き合い方2022年版
quramy
36
13k
Docker and Python
trallard
37
2.9k
BBQ
matthewcrist
82
9k
Happy Clients
brianwarren
94
6.6k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
16
1.6k
Statistics for Hackers
jakevdp
792
220k
In The Pink: A Labor of Love
frogandcode
139
22k
What's new in Ruby 2.0
geeforr
338
31k
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]