In revision control systems, a repository[1] is a data structure that stores metadata for a set of files or directory structure. Depending on whether the version control system in use is distributed like (Git or Mercurial) or centralized like (Subversion, CVS, or Perforce), the whole set of information in the repository may be duplicated on every user's system or may be maintained on a single server.[2] 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.
- A set of references to commit objects, called heads.
Storing changes
The main purpose of a repository is to store a set of files, as well as the history of changes made to those files.[3] Exactly how each revision control system handles storing those changes, however, differs greatly: for instance, Subversion has in the past relied on a database instance and has since moved to storing its changes directly on the filesystem.[4] These differences in methodology have generally led to diverse uses of revision control by different groups, depending on their needs.[5]
See also
- Software repository
- Codebase
- Forge (software)
- Comparison of source code hosting facilities
References
- ^ "SVNBook". Retrieved 2012-04-20.
- ^ "Version control concepts and best practices". 2018-03-03. Archived from the original on 2020-04-27. Retrieved 2020-07-10.
- ^ "Getting Started - About Version Control". Git SCM.
- ^ Ben Collins-Sussman; Brian W. Fitzpatrick; C. Michael Pilato (2011). "Chapter 5: Strategies for Repository Deployment". Version Control with Subversion: For Subversion 1.7. O'Reilly.
- ^ "Different approaches to source control branching". Stack Overflow. Retrieved 15 November 2014.