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
Intro to GitHub
Search
Alex Campbell
January 22, 2015
Programming
1
95
Intro to GitHub
An introduction to github (not git) for my data engineering class
Alex Campbell
January 22, 2015
Tweet
Share
More Decks by Alex Campbell
See All by Alex Campbell
HackCU Oh the Places You'll Go
zandrr
0
49
Other Decks in Programming
See All in Programming
Node-RED を(HTTP で)つなげる MCP サーバーを作ってみた
highu
0
110
Cursor AI Agentと伴走する アプリケーションの高速リプレイス
daisuketakeda
1
130
LT 2025-06-30: プロダクトエンジニアの役割
yamamotok
0
550
明示と暗黙 ー PHPとGoの インターフェイスの違いを知る
shimabox
2
380
XP, Testing and ninja testing
m_seki
3
210
PicoRuby on Rails
makicamel
2
110
What Spring Developers Should Know About Jakarta EE
ivargrimstad
0
300
「Cursor/Devin全社導入の理想と現実」のその後
saitoryc
0
330
エンジニア向け採用ピッチ資料
inusan
0
160
Enterprise Web App. Development (2): Version Control Tool Training Ver. 5.1
knakagawa
1
120
PHP 8.4の新機能「プロパティフック」から学ぶオブジェクト指向設計とリスコフの置換原則
kentaroutakeda
2
660
ReadMoreTextView
fornewid
1
480
Featured
See All Featured
Unsuck your backbone
ammeep
671
58k
ReactJS: Keep Simple. Everything can be a component!
pedronauck
667
120k
A Modern Web Designer's Workflow
chriscoyier
694
190k
GitHub's CSS Performance
jonrohan
1031
460k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
PRO
181
53k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
Building Applications with DynamoDB
mza
95
6.5k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.4k
Bash Introduction
62gerente
614
210k
How To Stay Up To Date on Web Technology
chriscoyier
790
250k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
281
13k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
34
3k
Transcript
INTRO TO GITHUB How to become a sir while githubbing
AGENDA • GitHub Workflow • Branch • Commit • Pull
Request • Discuss and Review • Merge and Deploy • Let’s Do it For Reals: • <Insert Live Demo Here> • Forking • Pull Requests • Issues Let’s assume you have your Git-Fu down.
GITHUB WORKFLOW Yeah, it’s that simple.
CREATE A BRANCH git checkout -b “monocles-for-everyone”
PRO-TIP Anything on the master branch is ALWAYS deployable to
production. mmm so high-res :shipit:
ADD SOME COMMITS git commit -m “so many monocles”
PRO-TIP Write clear commit messages so that people know what
the hell you’re doing. GIT COMMIT -M “FIXED ERRORS IN THE PREVIOUS COMMIT”
OPEN A PULL REQUEST You’re well on your way to
GitHub sir-ism
PRO-TIP 1) Use ‘@mention’! 2) Use Fork/Pull model for open
source repos to notify maintainers! 3) Use Pull requests to help start a conversation with your group, if repo is shared!
FORK? ‘SPLAIN YOURSELF. A fork is an exact copy of
a repository. Use it to run experiments without screwing anything up.
FORK > BRANCH? well it depends on what you’re doing.
VS
DISCUSS AND REVIEW CODE Remember, we’re collaborating here.
PRO-TIP Pull request comments support emojis :thumbsup:
MERGE AND DEPLOY You’ve done it, sir.
PRO-TIP Secret keywords do cool stuff in commit messages: “created
landing page Closes #32” I <3 DOCS
A QUICK REVIEW Someone explain this to me.
LIVE DEMO Let’s hope this guy knows what he’s doing…