Summary and Schedule
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:
Nothing that is committed to version control is ever lost, unless you work really, really hard at losing it. Since all old versions of files are saved, it’s always possible to go back in time to see exactly who wrote what on a particular day, or what version of a program was used to generate a particular set of results.
As we have this record of who made what changes when, we know who to ask if we have questions later on, and, if needed, revert to a previous version, much like the “undo” feature in an editor.
When several people collaborate in the same project, it’s possible to accidentally overlook or overwrite someone’s changes. The version control system automatically notifies users whenever there’s a conflict between one person’s work and another’s.
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.
|Download files required for the lesson
|Duration: 00h 00m
|1. Automated Version Control
|What is version control and why should I use it?
|Duration: 00h 05m
|2. Setting Up Git
|How do I get set up to use Git?
|Duration: 00h 10m
|3. Creating a Repository
|Where does Git store information?
|Duration: 00h 20m
|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?
|Duration: 00h 40m
|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?
|Duration: 01h 05m
|6. Ignoring Things
|How can I tell Git to ignore files I don’t want to track?
|Duration: 01h 10m
|7. Remotes in GitHub
|How do I share my changes with others on the web?
|Duration: 01h 55m
|How can I use version control to collaborate with other people?
|Duration: 02h 20m
|What do I do when my changes conflict with someone else’s?
|Duration: 02h 35m
|10. Open Science
|How can version control help me make my work more open?
|Duration: 02h 45m
|What licensing information should I include with my work?
|Duration: 02h 50m
|How can I make my work easier to cite?
|Duration: 02h 52m
|Where should I host my version control repositories?
|Duration: 03h 02m
|14. Supplemental: Using Git from RStudio
|How can I use Git with RStudio?
|Duration: 03h 12m
The actual schedule may vary slightly depending on the topics and exercises chosen by the instructor.
Since several Carpentries lessons rely on Git, please see this section of the workshop template for instructions on installing Git for various operating systems.
You will need an account for GitHub to follow episodes 7 & 8 in this lesson.
- Go to https://github.com and follow the “Sign up” link at the top-right of the window.
- Follow the instructions to create an account.
- Verify your email address with GitHub.
- Configure multifactor authentication (see below).
In 2023, GitHub introduced a requirement for all accounts to have multi-factor authentication (2FA) configured for extra security. Several options exist for setting up 2FA, which are summarised here:
- If you already use an authenticator app, like Google Authenticator or Duo Mobile on your smartphone for example, add GitHub to that app.
- If you have access to a smartphone but do not already use an authenticator app, install one and add GitHub to the app.
- If you do not have access to a smartphone or do not want to install an authenticator app, you have two options:
The GitHub documentation provides more details about configuring 2FA.
We’ll do our work in the
Desktop folder so make sure you
change your working directory to it with:
$ cd Desktop