What is version control?

Version control is a system, most commonly Git, that records every change made to a website’s code over time so developers can review history, collaborate and undo mistakes.

Curious how your site handles version control?

Send me the address. I’ll look under the hood and tell you plainly what I find, free.

No newsletter. Just what you asked for, from me. Privacy

In plain English

Each saved change, called a commit, records what changed, who changed it and why. Developers can compare versions, work on features separately and roll back to a known good state.

The code usually lives in a repository on a service like GitHub or GitLab. That repository is the authoritative copy of the site’s code.

Why it matters for a small business

Without version control, a bad change can be hard to undo and nobody can say exactly what changed. With it, your site’s history is documented. It also matters for ownership: whoever controls the repository effectively controls the code.

An example

A Calgary law firm’s site breaks after a developer edits a template directly on the live server, with no record of the old version. On a site under version control, the same mistake would be reverted to the previous commit in minutes, and the firm would hold access to the repository itself.

Common mistakes

Where I see version control go wrong most often.

  1. Editing files directly on the live server instead of through the repository.

  2. Letting the only copy of the repository sit in a developer’s personal account.

  3. Committing passwords or API keys into the repository history.

FAQ

Version control, answered

  1. Not exactly. It tracks code history. You still need backups of content, databases and uploads that aren’t in the repository.

  2. Yes. Owning or having access to the repository means you can move to another developer without starting over.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk