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
(2024-2025) CHI Grad Fellowship - Version Control
Search
Ethan Watrall
October 24, 2024
Education
0
33
(2024-2025) CHI Grad Fellowship - Version Control
Ethan Watrall
October 24, 2024
Tweet
Share
More Decks by Ethan Watrall
See All by Ethan Watrall
Make it Useful, Make it Usable: Heritage, Archaeological, and Museum Data in the 21st Century
watrall
0
220
Mbira: A Platform to Build, Serve, and Sustain Mobile Heritage Experiences
watrall
0
230
Towards a Model of Collaborative & Interdisciplinary Digital Cultural Heritage
watrall
1
310
Methods and Models for Building Capacity in Digital Cultural Heritage
watrall
0
420
Towards a Model of Openness in Digital Cultural Heritage
watrall
0
260
msu.seum: A location-based mobile app for exploring the cultural heritage and archaeology of MSU
watrall
0
330
Big Data, Small Stories: community, collaboration, & user experience in the age of digital cultural heritage
watrall
1
580
Archaeology and the Big Tent of the Digital Humanities
watrall
1
250
KORA: Open Source Digital Repository Platform for Cultural Heritage
watrall
0
580
Other Decks in Education
See All in Education
著作権と授業に関する出前講習会/dme-2025-05-01
gnutar
0
210
情報科学類で学べる専門科目38選
momeemt
0
230
新卒研修に仕掛ける 学びのサイクル / Implementing Learning Cycles in New Graduate Training
takashi_toyosaki
1
180
2025年度春学期 統計学 第2回 統計資料の収集と読み方(講義後配付用) (2025. 4. 17)
akiraasano
PRO
0
120
プレゼンテーション実践
takenawa
0
10k
Tutorial: Foundations of Blind Source Separation and Its Advances in Spatial Self-Supervised Learning
yoshipon
1
130
シリコンバレーでスタートアップを共同創業したファウンディングエンジニアとしての学び
tomoima525
0
210
Pythonパッケージ管理 [uv] 完全入門
mickey_kubo
20
17k
モンテカルロ法(3) 発展的アルゴリズム / Simulation 04
kaityo256
PRO
7
1.4k
Implicit and Cross-Device Interaction - Lecture 10 - Next Generation User Interfaces (4018166FNR)
signer
PRO
2
1.7k
アントレプレナーシップ教育 ~ 自分で自分の幸せを決めるために ~
yoshizaki
0
150
Case Studies and Course Review - Lecture 12 - Information Visualisation (4019538FNR)
signer
PRO
1
2k
Featured
See All Featured
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
danielanewman
229
22k
What’s in a name? Adding method to the madness
productmarketing
PRO
23
3.6k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
357
30k
Unsuck your backbone
ammeep
671
58k
How to Think Like a Performance Engineer
csswizardry
25
1.8k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
44
2.4k
VelocityConf: Rendering Performance Case Studies
addyosmani
332
24k
Optimising Largest Contentful Paint
csswizardry
37
3.4k
Building Flexible Design Systems
yeseniaperezcruz
328
39k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
130
19k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
234
17k
YesSQL, Process and Tooling at Scale
rocio
173
14k
Transcript
UNDERSTANDING VERSION CONTROL
Version control is a system that records changes to a
fi le or set of fi les over time so that you can recall speci fi c versions later. VERSION/SOURCE CONTROL
WHY?
DISTRIBUTED VERSION CONTROL ➋ ➋ CENTRALIZED VERSION CONTROL LOCAL VERSION
CONTROL ➊
None
None
None
None
None
None
None
None
None
(SOME IMPORTANT GITHUB TERMS)
The project. Collection of fi les that comprise the project.
Resides in a central (and accessible) location (the repository) A REPOSITORY
duplication of an object under revision control (such as a
source code fi le, or a document) so that modi fi cations can happen in parallel along both branches. In GitHub main branch is always now called main A BRANCH
when developers take a copy of source code from one
software package and start independent development on it, creating a distinct piece of software. FORKING
Copying all of the fi les from a repository to
your local machine (for editing, etc) CLONING
submitting the latest changes of the source code to the
repository, and making these changes part of the repository (any branch) COMMITTING
A request by the person who forked the repository to
roll any changes they made back into the main (original) repository. PULL REQUEST
WEB VS DESKTOP
THE DESKTOP ALWAYS USE
3RD PARTY CLIENTS
CODING COLLABORATIVELY
COLLABORATIVE WORKFLOW
DO WORK LOCALLY USING GITHUB DESKTOP w ➋ CLONE REPOSITORY
CREATE A REPOSITORY ➊ ADD COLLABORATORS x COLLABORATORS CLONE REPOSITORY y COLLABORATORS WORK LOCALLY USING GITHUB DESKTOP z
FETCH ORIGIN WHEN YOU START WORKING w ➋ COMMIT WHEN
YOU STOP WORKING WRITE A GOOD COMMIT MESSAGE ➊ WORK LOCALLY x ALWAYS NEVER EDIT ON THE WEB IN COLLABORATIVE PROJECT y
GITHUB AS PM TOOL
GITHUB AS WEB HOST
THE END