Version Control with Git

Wolfman and Dracula have been hired by Universal Missions (a space services spinoff from Euphoric State University) to investigate if it is possible to send their next planetary lander to Mars. They want to be able to work on the plans at the same time, but they have run into problems doing this in the past. If they take turns, each one will spend a lot of time waiting for the other to finish, but if they work on their own copies and email changes back and forth things will be lost, overwritten, or duplicated.

A colleague suggests using version control to manage their work. Version control is better than mailing files back and forth:

Teams are not the only ones to benefit from version control: lone researchers can benefit immensely. Keeping a record of what was changed, when, and why is extremely useful for all researchers if they ever need to come back to the project later on (e.g., a year later, when memory has faded).

Version control is the lab notebook of the digital world: it’s what professionals use to keep track of what they’ve done and to collaborate with other people. Every large software development project relies on it, and most programmers use it for their small jobs as well. And it isn’t just for software: books, papers, small data sets, and anything that changes over time or needs to be shared can and should be stored in a version control system.

Prerequisites

In this lesson we use Git from the Unix Shell. You will need to be somewhat comfortable with navigating your filesystem with the Unix Shell to make the most of this lesson.

Schedule

Setup Download files required for the lesson
00:00 1. Automated Version Control What is version control and why should I use it?
00:05 2. Setting Up Git How do I get set up to use Git?
00:40 3. Creating a Repository Where does Git store information?
00:50 4. Tracking Changes How do I record changes in Git?
How do I check the status of my version control repository?
How do I record notes about what changes I made and why?
01:10 5. Exploring History How can I identify old versions of files?
How do I review my changes?
How can I recover old versions of files?
01:35 6. Ignoring Things How can I tell Git to ignore files I don’t want to track?
01:40 7. Branches What are branches?
How can I work in parallel using branches?
02:00 8. Conflicts What do I do when my changes conflict?
02:15 9. Remotes in GitLab How do I share my changes with others on the web?
03:00 10. Merge Requests What are merge requests for?
How can I make a merge request?
04:15 11. Open Science How can version control help me make my work more open?
04:25 12. Licensing What licensing information should I include with my work?
04:30 13. Citation How can I make my work easier to cite?
04:32 14. Hosting Where should I host my version control repositories?
04:42 15. Using Git from RStudio How can I use Git with RStudio?
04:52 Finish

The actual schedule may vary slightly depending on the topics and exercises chosen by the instructor.