GitLab the Git Distributor View article history Edit article

Published: , Updated:
Talks about: <a class="post-tag post-tag-bitbucket" href="/tags/bitbucket">bitbucket</a>, <a class="post-tag post-tag-codeberg" href="/tags/codeberg">codeberg</a>, <a class="post-tag post-tag-git" href="/tags/git">git</a>, <a class="post-tag post-tag-github" href="/tags/github">github</a>, <a class="post-tag post-tag-gitlab" href="/tags/gitlab">gitlab</a>, and <a class="post-tag" href="/tags/"></a>

Git at its core is a decentralized version control system. Yet many people are relying on a single central server ( at the time of this writing) to share their work with others. Pro Git rightfully mentions it at first position in its chapter about distributed workflows because using a central server is usually the simplest approach to sharing code.

While the central server approach is easy to use, it might not work in all scenarios:

  1. An enterprise wants to share internal code as part of an open source project. All development is happening internally, and the public mirror gets an occasional update once in a while.
  2. To protect against outages of the central server, mirrors should be created and be kept up-to-date.

In case of the first scenario, tools like copybara, repoSpanner, or distributed-Git-forks offer a wide range of features to cover most details.

The second scenario can be solved manually with tools like gitomatic or automatically with GitLab’s mirror feature quite easy. GitLab allows to create a single pull-mirror and multiple push-mirrors. Therefore, it can be used to pull from your central server and push into all mirrors.

NOTE: This feature was previously available in the free tier but has now moved to GitLab Ultimate.

               |     GitHub     |               
         +-----|     GitLab     |------+        
         |     +----------------+      |        
         |                             |        
         |                             |        
         v                             v        
+----------------+            +----------------+
|    Codeberg    |            |    BitBucket   |
+----------------+            +----------------+

To create such a setup, follow these steps:

  1. Go to Settings > Repository and expand Mirroring repositories Code Flow
  2. Enter the URL of your central Git repository as the pull source, for example Code Flow
  3. Enter one push target for each mirror. Since pushing usually requires authentication, verify that the URL of the mirror contains a username, for example https://[email protected]/ Add an access token for each mirror and select password as authentication method. Code Flow

In case you prefer SSH keys over HTTP access tokens, just select SSH public key as authentication method and verify that your key is both saved in GitLab and all mirrors.