Simplify the "Repository mirroring" documentation
Problem to solve
The Repository mirroring docs page is very complex and difficult to understand.
Further details
N/A
Proposal
-
Mirroring should be explained in more detail, before getting into implementation details. For example:
- When is pull or push mirroring suitable?
- What prerequisites need to be addressed (authorisation, authentication, storage space)?
-
A table or diagram would help describe the mirroring options:
- From GitLab to A, B, C.
- From A, B, or C to GitLab*.
- From GitLab to GitLab.
For example, option 3 is required by anyone wanting to contribute to a GitLab project but does not have write access to that project. Perhaps here we could link to forking a GitLab repository, and how to keep it current?
-
There is no mention of how to monitor the mirroring process, either pull or push.
-
Perhaps we could add mention of how someone can manually keep
If I understand correctly, activity in a mirrored repository is reflected in the "target" repository, but under the account used to do the mirroring. Some users want the mirroring activity kept separate.
Who can address the issue
Anyone.