openskills.info
Course Preview

Version Control Fundamentals

Version control records changes to files over time so a team can inspect earlier versions, compare work, and combine concurrent edits. It uses a repository for history and a working copy for the files a person edits.

itComputer fundamentals

Version Control Fundamentals

Version control is a system that records changes to files or directories over time. It lets a person or team inspect an earlier state, compare two states, identify the change that introduced a problem, and restore a selected version. Source code is a common use case, but the model also applies to configuration, documentation, and other project files.

A version control system has two essential views of the same project. The repository stores the recorded history. A working copy is a local, editable view of one project state. Client software connects the working copy to the repository: it observes changes, records a new revision, and exchanges revisions with other copies or a shared service.

The unit of history

A recorded change is commonly called a revision or commit. It represents a deliberate project state plus enough metadata to place that state in history, such as an author, a time, a message, and a relationship to earlier revisions. The exact storage model differs by tool. Git records snapshots connected by parent relationships, while other systems can present history primarily as a sequence of revisions. The useful mental model is stable across tools: history is evidence, not a pile of renamed backup files.

Continue the course

This section is part of the paid course.

See pricing to subscribe, or log in if you already have access.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources