Install Git on a separate server
In this setup, we install the Git integration services on a separate server. It is assumed that TeamForge is installed on a separate server.
Set up a Git replica server
On sites distributed across multiple geographic locations, Git replica servers are local and remote mirror servers that can provide up to date copies of the central repositories, which if set up, can address load balancing and fetch performance issues. You can set up one or more Git replica servers (also referred to as slave or mirror servers) with TeamForge 8.1 and later.
Set up Large File Storage (LFS) for TeamForge repository
LFS is supported by TeamForge-Git/Gerrit integration 16.7.10-2.13.2 and later. LFS is controlled by two levels of configuration in TeamForge. First, integration level LFS configuration that provides default values for a given Gerrit instance. Second, repository level LFS configuration, which by default derives system level configuration that can be further adjusted.
Control the code review policy for Git repositories
With versions of the TeamForge–Git integration 6.2 and later, you can control all Gerrit Code Review features directly from TeamForge by specifying a code review policy as part of the TeamForge Git repository's description field.
TeamForge-Git integration: History protection
History rewrites are non-fast-forward updates of remote refs and associated objects. History rewrites happen when a branch in a remote repository gets deleted, previously pushed commits get amended or filtered and forcefully re-pushed, or a remote branch/tag is pointed to an entirely different commit history.
TeamForge-Git integration: FAQ
Use this background information to set up, maintain, support and work with the TeamForge-Git integration.
TeamForge Git integration reference
Look here for information on the mappings between TeamForge and Gerrit, Gerrit access rights, directory structure, connectivity, logs and configuration properties, and differences compared to vanilla Gerrit.