Repository

A repository (often shortened to repo) is an organised store for a project's source code together with the complete history of its changes. In practice it is not just a folder of files but a record of every modification: who changed what, when and why. That lets a team work in parallel, roll back to earlier versions and resolve conflicts in a controlled way.

How a repository works

Modern repositories are built on version control systems, the most popular of which is Git. The core concepts are:

• commit — a saved set of changes with a descriptive message,
• branch — a parallel line of development you can work on without affecting the main version,
• merge — folding a branch back into the mainline,
• history — the chronological chain of commits you can navigate.

A repository usually exists in two forms: local, on the developer's computer, and remote, on a platform such as GitHub or GitLab that acts as the team's shared synchronisation point.

Repositories in practice

The repository is the heart of the modern software development process. Around it you build branching workflows (such as gitflow), code review through pull requests, and CI/CD automation in which every pushed commit runs the test suite and, once it passes, triggers an automatic deployment to the server. Beyond code, repositories also store infrastructure configuration, documentation and design files. A well-kept repository with a readable commit history is one of the strongest signals of a team's technical maturity.