Summary and Schedule

Jimmy and Alfredo have been hired by Ratatouille restaurant (a special restaurant from Euphoric State University) to investigate if it is possible to make the best recipes archive ever. They want to be able to work on indexing the prices 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.

Prerequisites

In this lesson we use Git from the Unix Shell. Some previous experience with the shell is expected, but isn’t mandatory.

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

Installing Git

Installing Git on UKCEH Laptops

Git can be installed on UKCEH laptops through the Software Centre.

  1. Open the software center and type git in the search bar in the top-right.
  2. Locate Git on the list, click on it, and then click “Install”.
UKCEH Software Center
UKCEH Software Center

This will install Git and other utilities on your system, including GitBash. GitBash is a BASH emulator that we will use to provide a UNIX like command line to work with during the course of this carpentry course.

  1. Check the installation has been successful by opening the start menu, typing gitbash in the search bar and hitting enter.
  2. You should be greeted by a small, black, command line window. Type git --version and hit enter, you should receive similar information as below:
Git Bash
Git Bash

Other Systems

If you are using your own machine or a virtual machine, please refer to the carpentries instructions for installing Git on your chosen platform: - Git installation on Windows - Git installation on MacOS - Git installation on Linux

Creating a GitHub Account

You will need an account for GitHub to follow episodes 7 & 8 in this lesson.

  1. Go to https://github.com and follow the “Sign up” link at the top-right of the window.
  2. Follow the instructions to create an account.
  3. Verify your email address with GitHub.
  4. Configure multifactor authentication (see below).

Multi-factor Authentication

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:

  1. If you already use an authenticator app, like Google Authenticator or Duo Mobile on your smartphone for example, add GitHub to that app.
  2. If you have access to a smartphone but do not already use an authenticator app, install one and add GitHub to the app.
  3. If you do not have access to a smartphone or do not want to install an authenticator app, you have two options:
    1. set up 2FA via text message (list of countries where authentication by SMS is supported), or
    2. use a hardware security key like YubiKey or the Google Titan key.

The GitHub documentation provides more details about configuring 2FA.

GitHub Organisations

There are several UKCEH organisations you may want to join once you have created a GitHub account. To join any of these GitHub organisations please reach out to the relevant contact: - NERC-CEH (contact Rod Scott) - ukceh-rse (contact Joe Marsh Rossney)

This is entirely optional and this course can be completed without joinging these organisation, but we do recommend this so you can get visibility on what others are doing at UKCEH.

Preparing Your Working Directory

We’ll do our work in the Desktop folder so make sure you change your working directory to it with:

BASH 

$ cd
$ cd Desktop