When a mandatory review is specified, every change pushed to the repository must pass through a review process before it can get committed (merged) to the repository.
Only TeamForge users with the
Source Code Admin permission can bypass reviews.
Here's a list of permissions and what users with these permissions can do:
- No access: Users with no permissions cannot do anything.
- View only: Users with read permissions can read branches and push for reviews, and have -1 and +1 for reviews.
- Commit/View: Users with commit permissions can do everything read permissions would grant and in addition have -2, +2 for reviews. They can verify and submit permissions but have no right to bypass reviews.
- Delete/View: Users with delete permissions can do everything commit permissions would grant.
- Source Code Admin: Users with admin permissions can do everything delete permissions would grant and in addition push to and create any branch (bypassing review). They can rewrite history, forge the identity of the Gerrit server, and have the right to push tags, the right to upload merges, and the right to fine tune access rights in Gerrit for the Gerrit project involved.
Note: In TeamForge 6.2, the
code review policy for a Git repository is
defined in the Description field. If you had specified the
code review policy in TeamForge 6.2 and
have now upgraded TeamForge to version 8.0 or later, you will
see the appropriate code review option selected in the TeamForge user interface. The
Description field will still display the
[RepoCategory:<Category_name>], but you can remove it as it does not have any
effect in TeamForge.