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.

For more information on Gerrit Code Review, see the Gerrit documentation.

By default, the following code review policy options are provided:

Default (no code review): All Gerritreview features are turned off and read/write access is enforced.
Mandatory review: All code changes must be reviewed and read/write access is enforced.
Optional review: The review feature is turned on but can be bypassed if necessary; read/write access is enforced.
Custom: Access rights must be set manually in the Gerrit web interface; they will not be overridden by TeamForge. This specification is intended for advanced users who are familiar with Gerrit access rights and want to turn off “auto pilot”.
User-defined review: You can add your own categories, if you have access to the TeamForgeGerritMappings.xml file. For more information on adding a user-defined repository category, see Creat a User-defined Repository Category.

If you have access to the TeamForgeGerritMappings.xml file, you can add your own categories. The following animation illustrates the detailed mapping between SCM permissions, repository policies, and Gerrit access rights.