Issue 13 · Nov 2–8, 2026Editions · Glossary · Archive · Method · RSS · HU / ENG

News of the AI era, curated weekly

Glossary › Developer basics

checkout

advancedwidespread

Checkout is the operation by which you retrieve a selected version of a project from the version control system to work on it on your own machine.

In plain terms

Developers keep program source code in version control software. It preserves every previous state of the files in a repository and also manages multiple parallel working versions (branches). Checkout is the command that selects a version from this repository and makes it appear on your machine, in the working directory.

It is like library borrowing: every edition of a manual is in the warehouse, and you check out the one you need at the moment. The term comes from the everyday English phrase 'check out', which also means library borrowing.

It is useful for switching in seconds between a feature in development, the stable release, and the state of the code six months ago, without losing anything. Coding agents often use it too: before touching the code, they check out the appropriate branch or open a new one for the task.

Do not confuse it with the "checkout" page of online stores, where you pay for the contents of your cart. The word is the same, but the meaning is entirely different.

How it works

  1. You specify what you need: the name of a branch, a tagged release, or the identifier of a specific previous commit.
  2. The version control system checks whether there are uncommitted changes on your machine that the switch would overwrite. If so, it stops and warns you. Git simply carries changes that cause no conflict over to the new version.
  3. It replaces version-controlled files in the working directory so that you see the requested version: anything differing in that version is overwritten, and anything not included is removed. It does not touch files never saved or not tracked by the version control system.
  4. It switches the internal 'where I am' marker (called HEAD in Git), so your next saves go to the selected branch.
  5. The previous version is not lost: it remains in the repository, and you can return to it at any time with another checkout.

An everyday example

You ask a coding agent to fix an error on your company website. In its log, you see: "git checkout -b hibajavitas", meaning it opened a separate branch and switched to it so the fix does not touch the live version. If automatic tests run on GitHub, the first step there is also "actions/checkout", which retrieves the code.

Who is affected

developerYou use it many times a day when switching between branches, reviewing old states, or picking up someone else's work for testing. → Code
entrepreneur, executiveIf a coding agent works on the company's software, the checkout entry in the log shows which version it worked on and whether it touched the live code.
parent, student, teacherAnyone learning to program encounters it among the first lessons in version control, and it helps to understand why files 'disappear' when you switch. → Education & Family

A common misconception

MythCheckout downloads the project from the internet, or saves my work.
In realityIn Git, checkout retrieves a version only from the repository on your own machine; downloading is handled by clone and fetch, and saving is the job of commit. In older, centralized systems (such as Subversion), however, checkout actually retrieves the working copy from the server.

Limits and risks

Similar, but not the same

Related concepts

Broader

version control, Git

Narrower

detached HEAD

On the edge

branch, commit, cloning, storage, munkafa

A brief history

The term entered early version control systems from the English word for library lending, where a file's "checkout" also locked it for others. Git, released in 2005, uses it for version switching on your own machine; Git 2.23, released in 2019, introduced the switch and restore commands alongside it to separate the two tasks.

Where things stand

As of late 2026, checkout is a basic everyday operation in software development and almost always the first step in the workflows of coding agents and automated testing systems. In Git, switch and restore are gradually spreading alongside it, but the old command remains and is widely used.

Status: 2026 November

In the news

Appears in 20 Agent Age stories; the curve shows weekly occurrence in the news magazine.

Also known as

checkout · check-out · check out · git checkout · checkout · exception · branch switching · git switch

Sources

This entry was machine-edited and has undergone machine expert review; the “In the news” section updates automatically from Agent Age stories.