Jump to content

Commit (version control)

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by SamB (talk | contribs) at 21:33, 6 June 2015 (split content from Commit (data management)). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)

Commits are also done for revision control systems for source code such as Subversion, Git or CVS. A commit in the context of these version control systems refers to submitting the latest changes of the source code to the repository, and making these changes part of the head revision of the repository. Thus, when other users do an UPDATE or a checkout from the repository, they will receive the latest committed version, unless they specify they wish to retrieve a previous version of the source code in the repository. Version control systems also have similar functionality to SQL databases in that they allow rolling back to previous versions easily. In this context, a commit within a version control system is protected as it is easily rolled back, even after the commit has been done.