---
sourceDocument: Xanadu Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/application-development

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Code reviews

# Code reviews {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 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, users with the teamdev_code_reviewer role receive notifications to review
changes and can approve or reject changes. The Team Development Code Reviewers has the
teamdev_code_reviewer role.  
For each change, reviewers can see the following information.

* Which [remote
  instance](https://www.servicenow.com/docs/0lZrLqzVwRXgQTBCzU~kkw "For each instance, define other instances in the hierarchy as remote instances.") 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.
{#c_CodeReview__ul_fhh_sfv_1q}

Reviewers must approve or reject a push from the Team Development application.  
While changes are being reviewed on the parent instance, a child instance cannot 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.
{#c_CodeReview__ul_q4s_zfv_1q}