When an optional review is specified, every change submitted to the repository can be pushed for code review or directly pushed to the repository bypassing review. This depends on the TeamForge user having the appropriate permissions — source code Delete/View or Commit/View permission for the former, or Source Code Admin permission for the latter.
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, push to/create any branch (bypassing review) and push tags.
- Delete/View: Users with delete permissions can do everything commit permissions would grant and in addition, have the right to rewrite history, upload merges and forge identity.
- Source Code Admin: Users with admin permissions can do everything delete permissions would grant and in addition push to/create any branch (bypassing review). They can rewrite history, forge the identity of the Git server, and have the right to push tags, the right to upload merges, and the right to fine tune access rights in Git for the Git 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.