Open topic with navigation
Next to the Branches label, a drop-down button for each branch is displayed, plus an Add Branch button.
In the Paths field, enter one or more branch paths, one per line.
Optionally, check the Only Moderators can approve or reject reviews checkbox.
When checked, a field is displayed, allowing you to add a new moderator. The field auto-suggests groups and users within the Helix Versioning Engine as you type.
If a group is specified as a moderator, all of the members of that group have the same moderator privileges for that project branch as if they were added individually.
Once the branch specification is complete and the project has been saved, changing the state of any review associated with this moderated branch is restricted as follows:
The review's author, when she is not a moderator, can change the review's state to Needs Review, Needs Revision, Archived, and can attach committed changelists.
Normally, the review's author cannot change the review's state to Approved or Rejected on moderated branches. However, authors that are also moderators have moderator privileges, and may approve or reject their own review.
disable_self_approve is enabled, authors who are moderators (or even users with admin privileges) cannot approve their own reviews.
For the review's author and project members, if a review is not in one of their permitted states, for example if the review's state is Rejected, they cannot transition the review to another state.
These restrictions have no effect on who can start a review.
Click Done to accept your branch specification.
Once the branch definition has completed, if any moderators were specified, the number of moderators for that branch is displayed in the list of branches.
The project name does not need to be included in the branch name; Swarm displays the project name with the branch name when appropriate.