Version control is a system that tracks changes to files over time, recording who changed what, when, and why. It enables multiple people to work on the same files without overwriting each other’s changes, and makes it possible to revert to any previous state.
Git is the dominant version control system in software development. Other systems include Subversion (SVN) and Mercurial, though their usage has declined significantly.
You’ll hear this when…
“Is that in version control?” means “is that file being tracked?” If the answer is no, changes can be lost and there’s no history. Putting something in version control is the first step in professional software development.
Version control is so fundamental that it’s often invisible — it’s assumed. But the concepts matter: committing changes, branching for parallel work, merging contributions, resolving conflicts when two people edit the same section. These are daily activities for every developer.
Beyond code
Version control isn’t just for software. Design teams version their files. Technical writers version documentation. Data teams version database schemas and analysis notebooks. Any work that changes over time and relies on history and collaboration can benefit from version control. Tools like Git are engineered for code, but the principle is universal.
Source: Git documentation