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
Zendeskのチケットを Amazon Bedrockで 解析した
ryokosuge
3
300
さようなら Date。 ようこそTemporal! 3年間先行利用して得られた知見の共有
8beeeaaat
3
1.4k
Namespace and Its Future
tagomoris
6
700
AI時代のUIはどこへ行く?
yusukebe
18
8.9k
AIコーディングAgentとの向き合い方
eycjur
0
270
Navigation 2 を 3 に移行する(予定)ためにやったこと
yokomii
0
170
AIと私たちの学習の変化を考える - Claude Codeの学習モードを例に
azukiazusa1
10
4k
The Past, Present, and Future of Enterprise Java
ivargrimstad
0
370
2025 年のコーディングエージェントの現在地とエンジニアの仕事の変化について
azukiazusa1
24
12k
Introducing ReActionView: A new ActionView-compatible ERB Engine @ Rails World 2025, Amsterdam
marcoroth
0
690
為你自己學 Python - 冷知識篇
eddie
1
350
私の後悔をAWS DMSで解決した話
hiramax
4
210
Featured
See All Featured
The Invisible Side of Design
smashingmag
301
51k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
840
Rails Girls Zürich Keynote
gr2m
95
14k
Navigating Team Friction
lara
189
15k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
44
2.5k
Unsuck your backbone
ammeep
671
58k
Intergalactic Javascript Robots from Outer Space
tanoku
272
27k
Speed Design
sergeychernyshev
32
1.1k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.1k
Build your cross-platform service in a week with App Engine
jlugia
231
18k
Fireside Chat
paigeccino
39
3.6k
Agile that works and the tools we love
rasmusluckow
330
21k
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…