Skip to main content

Glossary R

Glossary · E-commerce

Repository

Area
E-commerce

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

The easiest way to picture a repository, says the 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.

Where the term appears

Sources

  1. GitHub-Glossar (deutsche Fassung) (opens in a new tab)

    GitHub Docs (docs.github.com) accessed

  2. Composer Documentation: Repositories (opens in a new tab)

    Composer (getcomposer.org) accessed

Share on LinkedIn

Let's talk about your project.

If this term is on your desk right now, a conversation usually helps faster than any definition.

Search the website

Popular topics

All results