Version Control with Mercurial

Version control is the lab notebook of the digital world: it's what software developers 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: instructional materials (like this), papers, theses, small data sets, and anything that changes over time or needs to be shared can and should be stored in a version control system.

Version control is better than emailing files back and forth because:

  • Nothing that is committed to version control is ever lost. This means it can be used like the "undo" feature in an editor, and 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.
  • It keeps a record of who made what changes when, so that if people have questions later on they know who to ask.
  • With version control it is hard (but not impossible) 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.

This workshop shows how to use a popular open source version control system called Mercurial (also known as hg). It is widely used, both because it's easy to set up, and because of a hosting site called Bitbucket. No matter which version control system you use, the most important thing to learn is not the details of their more obscure commands, but the workflow that they encourage.

Getting Ready

Follow the setup instructions to install Mercurial or TortoiseHg, and KDiff3 on your laptop. If you are working on Windows, TortoiseHg is the easiest way to get everything (including KDiff3) installed.

Topics

The Basics

  1. Setup Instructions
  2. Configuring Mercurial
  3. Creating a Repository
  4. Tracking Files

Day-to-Day Mercurial

  1. Making Changes
  2. Exploring History
  3. Recovering Old Versions
  4. Ignoring Things

Reaching Out

  1. Remote Repositories
  2. Working with Clone Repositories
  3. Collaboration
  4. Merging Changes from Different Clones
  5. Merge Conflicts

Digging Deeper

  1. Working with Non-Text Files
  2. Other Topics

Other Resources

Some of the instructional material in this workshop is based on the Software Carpentry Foundation lesson that introduces Version Control with Mercurial. The design of the web pages is also adapted from the Software Carpentry lessons pages.