gitlab-org--gitlab-foss/doc/security/information_exclusivity.md

1.9 KiB

stage group info type
Manage Authentication and Authorization To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments concepts

Information exclusivity (FREE)

Git is a distributed version control system (DVCS). This means that everyone who works with the source code has a local copy of the complete repository.

In GitLab every project member that is not a guest (reporters, developers, and maintainers) can clone the repository to create a local copy. After obtaining a local copy, the user can upload the full repository anywhere, including to another project that is under their control, or onto another server.

Therefore, it is impossible to build access controls that prevent the intentional sharing of source code by users that have access to the source code.

This is an inherent feature of a DVCS. All Git management systems have this limitation.

You can take steps to prevent unintentional sharing and information destruction. This limitation is the reason why only certain people are allowed to add users to a project and why only a GitLab administrator can force push a protected branch.