---
title: "Repository"
description: "A repository stores a project's source code together with its full change history. Learn about Git repos, branches, commits and team collaboration."
url: "https://nodea.io/en/glossary/repository"
lang: "en"
updated: "2026-07-13"
---

# Repository

> A repository is an organised store for a project's source code together with the complete history of its changes, enabling many developers to work together.

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](https://nodea.io/en/glossary/version-control) systems, the most popular of which is [Git](https://nodea.io/en/glossary/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](https://nodea.io/en/glossary/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](https://nodea.io/en/glossary/ci-cd) automation in which every pushed commit runs the test suite and, once it passes, triggers an automatic [deployment](https://nodea.io/en/glossary/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.

### What is the difference between a local and a remote repository?

A local repository lives on the developer's machine and lets you work and commit changes offline. A remote repository, hosted on a service like GitHub or GitLab, is the shared synchronisation point for the whole team — you push changes to it and pull changes from it.

### Does a repository have to be private?

No. A repository can be public and visible to anyone (typical for open-source projects) or private and accessible only to authorised users. The owner controls visibility in the hosting platform's settings.

## Related

- [Git](https://nodea.io/en/glossary/git)
- [GitHub](https://nodea.io/en/glossary/github)
- [Version control](https://nodea.io/en/glossary/version-control)
- [CI/CD](https://nodea.io/en/glossary/ci-cd)
- [Deploy](https://nodea.io/en/glossary/deployment)

---

Languages: [pl](https://nodea.pl/pl/slownik-pojec/repozytorium.md)  
Site index: [llms.txt](https://nodea.io/en/llms.txt)