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
210
HackRU2013-GH
Git, GitHub, and workflows.
Brian Levine
March 28, 2013
Tweet
Share
Other Decks in Programming
See All in Programming
Androidアプリの One Experience リリース
nein37
0
720
PHPとAPI Platformで作る本格的なWeb APIアプリケーション(入門編) / phpcon 2024 Intro to API Platform
ttskch
0
360
HTML/CSS超絶浅い説明
yuki0329
0
160
良いユニットテストを書こう
mototakatsu
11
3.5k
AWSのLambdaで PHPを動かす選択肢
rinchoku
2
360
開発者とQAの越境で自動テストが増える開発プロセスを実現する
92thunder
1
220
PHPで学ぶプログラミングの教訓 / Lessons in Programming Learned through PHP
nrslib
4
1k
Compose UIテストを使った統合テスト
hiroaki404
0
120
Fixstars高速化コンテスト2024準優勝解法
eijirou
0
170
為你自己學 Python
eddie
0
500
GitHub CopilotでTypeScriptの コード生成するワザップ
starfish719
26
5.8k
Cloudflare MCP ServerでClaude Desktop からWeb APIを構築
kutakutat
1
630
Featured
See All Featured
A Tale of Four Properties
chriscoyier
157
23k
The Power of CSS Pseudo Elements
geoffreycrofte
74
5.4k
Statistics for Hackers
jakevdp
797
220k
Intergalactic Javascript Robots from Outer Space
tanoku
270
27k
Music & Morning Musume
bryan
46
6.3k
Reflections from 52 weeks, 52 projects
jeffersonlam
348
20k
The Art of Programming - Codeland 2020
erikaheidi
53
13k
I Don’t Have Time: Getting Over the Fear to Launch Your Podcast
jcasabona
29
2k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
45
2.3k
Thoughts on Productivity
jonyablonski
68
4.4k
Scaling GitHub
holman
459
140k
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]