# Repository

> A repository (on GitHub, for example) holds a software project with all its files, its documentation and the revision history of every file.

Original page: https://t10.de/en/glossary/repository
Publisher: total10 GmbH, https://t10.de/en/glossary

The easiest way to picture a repository, says the [GitHub glossary](https://docs.github.com/en/get-started/learning-about-github/github-glossary), is as a project's folder. A remote repository, in the glossary's terms, belongs to the same project but is stored elsewhere. Git's own documentation says a repository is typically created in one of two ways: by turning a local directory into a Git repository or by cloning an existing one.

GitHub calls a personal copy of another user's repository a fork: changes can be made in it without affecting the original. Seen from a fork or a branch, the primary branch of the original repository is often called the upstream, since that is where most changes come from. The branch or fork being worked on is then the downstream.

Our own plugins for Shopware 5 shops are kept, with their history, in the shop repository. We keep track of Shopware 5's maintenance status through its official repository on GitHub. We take the packages we update from the upstream repositories, not from a fork.

For Composer, a repository is a package source: a list of packages and versions that Composer consults to find what a project needs. By default, only one is registered: Packagist.org. In a shop project, the word can therefore mean either the place where the code is kept or the source of the packages.

## See also

- [Composer](https://t10.de/en/glossary/composer): Composer is a tool for dependency management in PHP: a project declares the libraries it depends on, and Composer installs and updates them.
- [Software release](https://t10.de/en/glossary/software-release): A software release is a published, deployable version of a piece of software, made available under a fixed version number for download and installation.
- [Lock file](https://t10.de/en/glossary/lock-file): A lock file records the exact versions of all packages installed in a project, so that every installation ends up in the same state; with Composer it is composer.lock.

## Where the term appears

- [Shopware 5 end of life: what it means for your shop](https://t10.de/en/blog/shopware-5-end-of-support)
- [Shopware 5: end of vendor support](https://t10.de/en/merchant-radar/shopware-5-end-of-support)
- [Retrofitting a Shopware 5 shop for the legal duties of 2026 and 2027](https://t10.de/en/blog/shopware-5-new-legal-duties-2026-2027)

## Sources

1. [GitHub-Glossar (deutsche Fassung)](https://docs.github.com/de/get-started/learning-about-github/github-glossary), GitHub Docs (docs.github.com), accessed 2026-11-16
2. [Pro Git (2. Auflage, deutsche Übersetzung), 2.1 Git Grundlagen: Ein Git-Repository anlegen](https://git-scm.com/book/de/v2/Git-Grundlagen-Ein-Git-Repository-anlegen), Git Project (git-scm.com), accessed 2026-11-16
3. [Composer Documentation: Repositories](https://getcomposer.org/doc/05-repositories.md), Composer (getcomposer.org), accessed 2026-11-16
