Repository (version control)

In <a href="/facts/Version_control/pxCmFXqK">version control systems</a>, a repository is a data structure that stores <a href="/facts/Metadata/qt35z79C">metadata</a> for a set of files or <a href="/facts/Directory_structure/t7lEWPpd">directory structure</a>. Depending on whether the version control system in use is distributed, like <a href="/facts/Git/U5Ty9QmQ">Git</a> or <a href="/facts/Mercurial/lEkoYb6C">Mercurial</a>, or centralized, like <a href="/facts/Apache_Subversion/b5j9wAbt">Subversion</a>, <a href="/facts/Concurrent_Versions_System/PKnqSra2">CVS</a>, or <a href="/facts/Perforce/y9wI1f6T">Perforce</a>, the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single <a href="/facts/Server_(computing)/dEaYFD7r">server</a>. Some of the metadata that a repository contains includes, among other things, a historical record of changes in the repository, a set of commit objects, and a set of references to commit objects, called heads.
The main purpose of a repository is to store a set of files, as well as the history of changes made to those files. Exactly how each version control system handles storing those changes, however, differs greatly. For instance, Subversion in the past relied on a database instance but has since moved to storing its changes directly on the filesystem. These differences in storage techniques have generally led to diverse uses of version control by different groups, depending on their needs.

Repository (version control) open-in-new

Repository (version control)