Automated Version Control

Figure 1

Comic: a PhD student sends "FINAL.doc" to their supervisor, but after several increasingly intense and frustrating rounds of comments and revisions they end up with a file named "FINAL_rev.22.comments49.corrections.10.#@$%WHYDIDCOMETOGRADSCHOOL????.doc"
“notFinal.doc” by Jorge Cham, https://www.phdcomics.com

Figure 2

Changes Are Saved Sequentially

Figure 3

Different Versions Can be Saved

Figure 4

Multiple Versions Can be Merged

Setting Up Git

Creating a Repository

Figure 1

motivatingexampleWerewolf vs dracula by b-maze / Deviant Art. Mars by European Space Agency / CC-BY-SA 3.0 IGO. Pluto / Courtesy NASA/JPL-Caltech. Mummy © Gilad Fried / The Noun Project / CC BY 3.0. Moon © Luc Viatour / https://lucnix.be / CC BY-SA 3.0.

Tracking Changes

Figure 1

The Git Staging Area

Figure 2

The Git Commit Workflow

Exploring History

Figure 1

Git Staging
https://figshare.com/articles/How_Git_works_a_cartoon/1328266

Figure 2

Git Restore

Ignoring Things

Remotes in GitHub

Figure 1

Creating a Repository on GitHub (Step 1)

Figure 2

Creating a Repository on GitHub (Step 2)

Figure 3

Creating a Repository on GitHub (Step 3)

Figure 4

The Local Repository with Git Staging Area

Figure 5

Freshly-Made GitHub Repository

Figure 6

Where to Find Repository URL on GitHub

Figure 7

Changing the Repository URL on GitHub

Figure 8

GitHub Repository After First Push

Branches

Collaborative Version Control - Centralized

Collaborative Version Control - Distributed

Figure 1

Creating a fork of a repository (Step 1)

Figure 2

Select a location and a name for the fork (Step 2)

Figure 3

Your forked repository (Step 3)

Figure 4

Opening a Pull request from your fork into the original repository