repók

Repók (sing. repó) are the Hungarian term for repositories in computing, i.e., storage locations for code, data, or artifacts that are managed under a version-control system. The word derives from the English repository and is adapted to Hungarian spelling with the plural suffix -k.

In practice, repók are central to software development and DevOps; they can be stored locally on a developer’s machine or remotely on hosting services such as GitHub, GitLab, or an internal server. A repository stores the history of a project, including commits, branches, and tags, and can be either bare or non-bare. A non-bare repó has a working directory where files are checked out, while the .git directory contains the object database, commits, and refs. A bare repó lacks a working directory and is used primarily for sharing over networks. Some repók are dedicated to artifacts, such as package registries or container image repositories, and are managed by specialized tools.

Common operations associated with repók include clone, fetch, pull, push, commit, and merge. Repositories are typically connected to remotes, which are named locations for collaboration; the default name is often origin. Workflows vary from centralized to distributed version control, influencing how changes are proposed, reviewed, and integrated.

Examples in practice show that the most widely used distributed version control system is Git, whose repók can be hosted on platforms like GitHub, GitLab, Bitbucket, or private servers. The term repó is widely understood in IT contexts in Hungarian and remains a practical shorthand for discussing code bases, history, and collaboration within development teams.