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
Result型で“失敗”を型にするPHPコードの書き方
kajitack
4
530
地方に住むエンジニアの残酷な現実とキャリア論
ichimichi
5
1.4k
Select API from Kotlin Coroutine
jmatsu
1
190
VS Code Update for GitHub Copilot
74th
1
480
Goで作る、開発・CI環境
sin392
0
170
20250628_非エンジニアがバイブコーディングしてみた
ponponmikankan
0
520
Railsアプリケーションと パフォーマンスチューニング ー 秒間5万リクエストの モバイルオーダーシステムを支える事例 ー Rubyセミナー 大阪
falcon8823
4
1k
WindowInsetsだってテストしたい
ryunen344
1
200
エラーって何種類あるの?
kajitack
5
320
deno-redisの紹介とJSRパッケージの運用について (toranoana.deno #21)
uki00a
0
150
生成AIコーディングとの向き合い方、AIと共創するという考え方 / How to deal with generative AI coding and the concept of co-creating with AI
seike460
PRO
1
340
A2A プロトコルを試してみる
azukiazusa1
2
1.2k
Featured
See All Featured
We Have a Design System, Now What?
morganepeng
53
7.7k
Code Review Best Practice
trishagee
68
18k
The Cost Of JavaScript in 2023
addyosmani
51
8.5k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.9k
Thoughts on Productivity
jonyablonski
69
4.7k
A better future with KSS
kneath
239
17k
KATA
mclloyd
30
14k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2.1k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
13k
Git: the NoSQL Database
bkeepers
PRO
430
65k
The Myth of the Modular Monolith - Day 2 Keynote - Rails World 2024
eileencodes
26
2.9k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3.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…