Skip to main content
Legia

Apps & Software

What is Version Control?

Also called Git, revision control, source control.

Short definition

Version control is a system that records every change to source code, who made it and when, so teams can work at the same time, view the history, and roll back to a previous version if something goes wrong.

How it works

Code is stored in a repository. Each change is saved as a commit containing what changed, who made it, and an explanatory message. Developers can create separate branches for new features, then merge them into the main branch after review. Git is the most widely used version control system, and its repositories are usually hosted on services such as GitHub, GitLab, or a company-owned server.

Benefits for the company

A complete history makes every change traceable, including when a bug first appeared. A problematic release can be rolled back to the previous version quickly. Version control is also the foundation of CI/CD, because every commit can trigger automated testing and releases. Code review through merge requests, often called pull requests, ensures every change is read by a second person before it enters the main branch.

What to make sure of

Repositories should live in an account owned by the company, or at least be handed over when the project ends, in line with the source code ownership clause in the contract. Without access to the repository, the company holds only the finished application without its history and will struggle to switch vendors. Passwords, API keys, and secret configuration files must not be stored in the repository. If they were stored there by mistake, those secrets are considered leaked and need to be replaced, because the repository history keeps them even after the files are deleted.

Related Legia service DevOps & CI/CD Automated release pipelines, consistent environments, and monitoring that your own team can run.

Resources