Commit 664b433a authored by Sytse Sijbrandij's avatar Sytse Sijbrandij

Add explanation about unintentional sharing.

parent ff4a45ef
...@@ -6,3 +6,4 @@ In GitLab every project member that is not a guest (so reporters, developers and ...@@ -6,3 +6,4 @@ In GitLab every project member that is not a guest (so reporters, developers and
After obtaining this local copy the user can upload the full repository anywhere, including another project under their control or another server. After obtaining this local copy the user can upload the full repository anywhere, including another project under their control or another server.
The consequense is that you can't build access controls that prevent the intentional sharing of source code by users that have access to the source code. The consequense is that you can't 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 and all git management systems have this limitation. This is an inherent feature of a DVCS and all git management systems have this limitation.
Obviously you can take steps to prevent unintentional sharing and information destruction, this is why only some people are allowed to invite others and nobody can force push a protected branch.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment