Code reviews

  • Release version: Zurich
  • Updated July 31, 2025
  • 1 minute to read

    • Team Development administrators can require that pushes undergo code review before accepting pushes.

    When code review is enabled, pushing a change to the parent instance triggers the code review workflow. By default, the teamdev_code_reviewer role receives notifications to review changes and can approve or reject changes.

    Figure 1. Code review workflow
    Code review workflow.
    1. Starts when changes are pushed to the parent instance.
    2. Verifies that the code review property is active on the parent instance.
    3. Sets the state of the changes requiring approval to Awaiting Code Review.
    4. If configured Notifies the Team Development Code Reviewers group to review pushed changes.
    5. Loads the approved changes or sets the state to Code Changes Rejected.

    Change details

    For each change, reviewers can see the following information.
    • Which remote instance the pushed change comes from?
    • Who pushed the change to the parent?
    • What the change is called?
    • When the change was created?
    • Which versions the change includes?

    Reviewers must approve or reject a push from the Team Development application.

    Child instance restrictions

    While changes are being reviewed on the parent instance, a child instance can’t do the following activities involving the parent instance:
    • Push changes to the parent instance.
    • Pull changes from the parent instance.
    • Reconcile changes with the parent instance.
    • Change the parent instance to another instance.
    • Delete the remote instance record for the parent instance.