How do I manage project branches?

Initial steps:

  1. Visit your project page.
  2. Click Edit.

    Next to the Branches label, a drop-down button for each branch is displayed, and + Add Branch.

    Branches drop-down image

Adding a branch

  1. Follow the initial steps.
  2. Click + Add Branch to display the branch drop-down dialog.

    Image of the branch drop-down dialog

  3. Enter a short Name for your branch.
  4. Enter one or more branch paths in the Paths field, one per line.

    Note

    Each branch path should be expressed in depot syntax. Wildcards should not be used; the only exception is the branch path can end with the Helix Server wildcard ...

    For example: //depot/main/swarm/...

    For more information, see File Specifications in P4 Command Reference.

  5. Optional: specify Default Reviewers for the project branch.

    This field auto-suggests users, and groups within Helix Server as you type (up to a combined limit of 20 entries). Click on the user or group to add them as a default reviewer. Each time a new review is created, the default reviewers will be added to the review.

    Click the X icon to the right of the userid or groupid to remove that default reviewer from the default reviewers list.

    Important

    When a review is part of multiple projects/project branches:

    • The default reviewer lists for all of the projects and project branches the review is part of are combined and added to the review.
    • If a default reviewer has different reviewer options set on projects and project branches that the review is part of, the strictest reviewer option is used for the review.

    Example: A review is created and it is part of Project A, Project B, and Project Branch b.

    Project A: default reviewer X is an Optional reviewer

    Project B: default reviewer X is an Optional reviewer

    Project Branch b: default reviewer X is a Required reviewer

    Result: default reviewer X is added to the review as a Required reviewer

    Note

    If users or groups are @mentioned in a new changelist description that includes #review, they will be added to the review as reviewers. If any of these reviewers are already specified as default reviewers they will not be added to the review again, the reviewer's most restrictive reviewer option is used for the review.

    Note

    If a default reviewer is deleted from Helix Server they will not be added to new reviews.

  6. Optional: 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:

  7. 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.

  8. Click Save to save the branch changes to your project.
Note

The project name does not need to be included in the branch name; Swarm displays the project name with the branch name when appropriate.

Editing a branch

  1. Follow the initial steps.
  2. Click the branch drop-down button you want to edit.
  3. Revise the Name, Paths, default reviewers, or moderators as required.
  4. Click Save.

Removing a branch

  1. Follow the initial steps.
  2. Click the branch drop-down button you want to remove.
  3. Click Remove.
  4. Click Save.