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
git.pdf
Search
Christopher Prener
September 12, 2019
0
36
git.pdf
Christopher Prener
September 12, 2019
Tweet
Share
More Decks by Christopher Prener
See All by Christopher Prener
washu-lec
chrisprener
0
140
slu_ahead.pdf
chrisprener
0
230
fundamental-causes-psych
chrisprener
0
98
fundamental-causes- slu-geriatric
chrisprener
0
170
fundamental-causes-ances
chrisprener
0
440
stitching-across-data-seams-stlc
chrisprener
0
100
fundamental-causes-slu-med
chrisprener
0
82
data-seams-paa
chrisprener
0
150
ami_hospitalizations
chrisprener
0
70
Featured
See All Featured
The Art of Programming - Codeland 2020
erikaheidi
56
14k
Docker and Python
trallard
46
3.6k
The Web Performance Landscape in 2024 [PerfNow 2024]
tammyeverts
9
850
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
7
890
jQuery: Nuts, Bolts and Bling
dougneiner
64
7.9k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
35
3.2k
Optimizing for Happiness
mojombo
379
70k
Performance Is Good for Brains [We Love Speed 2024]
tammyeverts
12
1.2k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
285
14k
Site-Speed That Sticks
csswizardry
11
880
Stop Working from a Prison Cell
hatefulcrawdad
271
21k
Transcript
GIT AND GITHUB SLU DATA SCIENCE SEMINAR CHRISTOPHER PRENER, PH.D.
SEPTEMBER 12, 2019
KEY TERM A repository is a top-level directory that has
Git version control enabled.
GIT AND GITHUB TYPICAL WORKFLOW
GIT WORKFLOW GIT AND GITHUB TYPICAL WORKFLOW Commits are snapshots
of files that are saved at particular points in time.
GIT WORKFLOW GIT AND GITHUB TYPICAL WORKFLOW
GIT WORKFLOW GIT AND GITHUB TYPICAL WORKFLOW
GIT WORKFLOW GIT AND GITHUB TYPICAL WORKFLOW
GIT WORKFLOW GIT AND GITHUB TYPICAL WORKFLOW
GIT AND GITHUB TYPICAL WORKFLOW “OK, so why the $#&%
did I save a second copy?!?!?! And why the $#&% was the first copy edited after the second copy!?!?!?
GIT AND GITHUB GIT WORKFLOW
GIT AND GITHUB GIT WORKFLOW
GIT AND GITHUB GIT WORKFLOW
GIT AND GITHUB GIT WORKFLOW
GIT AND GITHUB GIT WORKFLOW Local repos can “sync” with
a “remote” repo, making backup and sharing easy
GIT AND GITHUB GIT WORKFLOW Copying data for the first
time from GitHub is called making a “clone”
GIT AND GITHUB GIT WORKFLOW Copying data for the first
time from GitHub is called making a “clone” Clone make changes Stage & Commit Push