Repository (version control)

Short description: Metadata storage for software revision control

In version control systems, a repository is a data structure that stores metadata for a set of files or directory structure.[1] 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, 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.[3] 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.[4] These differences in storage techniques have generally led to diverse uses of version control by different groups, depending on their needs.[5]

## Contents

* 1 Overview
* 2 Forges
* 2.1 Static web hosting
* 3 See also
* 4 References

## Overview

A repository being shown in GitLab, an open source code forge.

In software engineering, a version control system is used to keep track of versions of a set of files, usually to allow multiple developers to collaborate on a project. The repository keeps track of the files in the project, which is represented as a graph.

A Distributed version control system is made up of central and branch repositories. A central repository exists on the server. To make changes to it, a developer first works on a branch repository, and proceeds to commit the change to the former.

## Forges

A code forge is a web interface to a version control system. A user can commonly browse repositories and their constituent files on the page itself.

### Static web hosting

While forges are mainly used to perform version control operations, some forges allow users to host static web pages by uploading its source code (such as HTML and JavaScript, but not PHP) to a repository. This is usually done in order to provide documentation or a landing page for a software project.

The use of repositories as a place to upload web documents allows version control to be integrated, and additionally allows quick iteration because changes are pushed through the Version Control System instead of having to upload the file through a protocol like FTP.[6]

Examples of this kind of service include GitHub Pages and GitLab Pages.

## See also

* Sandbox (software development)
* Software repository
* Codebase
* Git
* Forge (software)
* Comparison of source-code-hosting facilities

## References

1. ↑ "SVNBook". http://svnbook.red-bean.com/en/1.7/svn.basic.version-control-basics.html#svn.basic.repository.
2. ↑ "Version control concepts and best practices". 2018-03-03. https://homes.cs.washington.edu/~mernst/advice/version-control.html.
3. ↑ "Getting Started - About Version Control". Git SCM. http://git-scm.com/book/en/v2/Getting-Started-About-Version-Control.
4. ↑ 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. http://svnbook.red-bean.com/en/1.7/svn.reposadmin.planning.html#svn.reposadmin.basics.backends.
5. ↑ "Different approaches to source control branching". https://stackoverflow.com/questions/1332746/different-approaches-to-source-control-branching.
6. ↑ "GitHub Pages | Websites for you and your projects, hosted directly from your GitHub repository.". https://pages.github.com/.

* v
* t
* e

Version control software

Years, where available, indicate the date of first stable release. Systems with names in italics are no longer maintained or have planned end-of-life dates.

Local only|

| Free/open-source|

* RCS (1982)
* SCCS (1972)

|

Proprietary|

* PVCS (1985)
* QVCS (1991)

Client–server|

| Free/open-source|

* CVS (1986, 1990 in C)
* CVSNT (1998)
* QVCS Enterprise (1998)
* Subversion (2000)

|

Proprietary|

* AccuRev SCM (2002)
* Azure DevOps
* Server (via TFVC) (2005)
* Services (via TFVC) (2014)
* ClearCase (1992)
* CMVC (1994)
* Dimensions CM (1980s)
* DSEE (1984)
* Endevor (1980s)
* Integrity (2001)
* Panvalet (1970s)
* Perforce Helix (1995)
* SCLM (1980s?)
* Software Change Manager (1970s)
* StarTeam (1995)
* Surround SCM (2002)
* Synergy (1990)
* Team Concert (2008)
* Vault (2003)
* Visual SourceSafe (1994)

Distributed|

| Free/open-source|

* ArX (2003)
* BitKeeper (2000)
* Codeville (2005)
* Darcs (2002)
* DCVS (2002)
* Fossil (2007)
* Git (2005)
* GNU arch (2001)
* GNU Bazaar (2005)
* Mercurial (2005)
* Monotone (2003)
* Veracity (2010)

|

Proprietary|

* Azure DevOps
* Server (via Git) (2013)
* Services (via Git) (2014)
* TeamWare (1992)
* Code Co-op (1997)
* Plastic SCM (2006)

Concepts|

* Baseline
* Branch
* Changeset
* Commit
* Data comparison
* Delta compression
* Fork
* Gated commit
* Interleaved deltas
* Merge
* Monorepo
* Repository
* Tag
* Trunk

* Category
* Comparison
* List

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Repository (version control). Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Repository_(version_control)&oldid=1182"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template