While I'm waiting for artwork, I'd be grateful for feedback on the script for the introductory episode on version control.
- Hello, and welcome to the first episode of the Software Carpentry lecture on version control. In this episode, we will explain what version control is, how it works, and why you should use it.
- Suppose you and a friend are working together on a paper.
- You both want to edit the file at the same time—what should you do?
- You could take turns, but then each of you would spend have the time waiting for the other.
- Another option would be to go ahead and work simultaneously, then patch things up afterward.
- But somehow, stuff always winds up getting lost, overwitten, or duplicated.
- The right solution is to use a version control system.
- This keeps the master copy of the file in a central repository, usually located on a server—a computer that is never used directly by people, but only by the applications serving them.
- No-one ever edits the master copy directly.
- Instead, you and your friend each have a working copy on your own computers.
- You work independently, making whatever changes you want to your local copies.
- As soon you are ready to share your changes, you commit your changes to the repository.
- Your friend can then update her working copy to get those changes.
- And of course, if your friend finishes her part first, she can commit, and then you can update.
- But what if you and your friend want to make changes to the same part of the paper?
- Old-fashioned version control systems prevented this from happening by locking the master copy. Everyone's working copy would normally be read-only. When someone wanted to start work on a file, the version control system would make her copy of that file writeable. When she was finished work, the version control system would copy her changes to the repository, then mark her copy as read-only once again.
- Only one person at a time could have a writeable copy. This guaranteed that two or more people could never accidentally make changes to the same file at the same time...
- ...but it also meant that only person at a time could work on any given file.
- This is essentially the "one at a time" strategy from the start of this episode, but with the version control system acting as the referee to prevent accidents.
- In practice, locking like this isn't as restrictive as it sounds. If you and your friend repeatedly find that you're trying to edit the same file, the solution is to break your paper (or your program) into several smaller files, so that you can work simultaneously.
- However, most of today's version control systems use a different strategy, one based on the old saying that it's easier to get forgiveness than permission. In these systems, nothing is ever locked—everyone is always allowed to edit the files in their working copy.
- Sometimes, of course, you and your friend will make changes to the same part of the paper.
- If your friend updates first first, her changes go into the repository as usual.
- If you try to commit something that would overwrite her changes, the version control system will stop you...
- ...and highlight the conflict by marking the overlapping regions in your working copy.
- It's up to you to edit the file to resolve the conflict. You can keep your changes, accept your friend's, or write something new that combines the two—it's up to you.
- Once you have fixed things, you can go ahead and commit.
- Experience shows that version control is better than mailing files back and forth for at least three reasons. First, it's hard (but not impossible) to accidentally overlook or overwrite someone's changes—the version control system highlights them for you automatically.
- Second, there are no arguments about whose copy is the most up to date—the master copy is.
- These features mean that version control is worth using even when you're the only person working on a particular set of files.
- Because it's a more reliable way to move files around between the computers you use than copying things onto a USB or sending email to yourself.
- More importantly, whether you're working on your own or in a group, version control allows you to look at or undo changes what you did weeks, months, or years ago.
- This works because the version control system never actually overwrites the master copy in the repository.
- Instead, everyone time someone commits a new version, the system saves it on top of the previous master copy, along with some information about when the change was made and who made it.
- This means that you can always see what the file looked like last week before someone rewrote the analysis section while you were on holiday.
- It also means that you can always fetch old versions of things, like the exact version of the program you used to produce the graph on page 5 of that paper that someone is now challenging.
- Version control systems do have one important shortcoming, though. If you are working with plain text files, it's easy for the version control system to find and display differences, and to help you merge them.
- Unfortunately, today's version control systems won't do this for images, MP3s, PDFs, and Microsoft Word or Excel files. These aren't stored as text—they use specialized binary data formats, and there usually aren't tools for finding, displaying, or merging the differences between them. In most cases, all the version system can do is say, "These files are different." That's better than nothing, but not by much.
- Even with this limitation, version control is probably the most important concept in this entire course. It's not just because it facilitates sharing; version control also allows you to look at or undo changes what you did weeks, months, or years ago.
- We'll talk more about using version control to make your research reproducible in a later lecture. In the next episode of this one, we'll look at the most popular open source version control system in use today, called Subversion.
The four episodes after this introduction will cover:
- the basic update/edit/commit cycle,
- merging conflicts,
- setting up a repository, and
- reverting to old versions of files.
Of these, #3 is the hardest, since we are not assuming people know how to use a shell or set up public/private keys. Not sure how to handle that yet; advice would be welcome.
Dialogue & Discussion
You can review our commenting policy here.