---
schema_version: "1"
id: 49cfe34fcbce6e1e66aa4a8497f6b626a496f1c49654b1208a08353d7e0b4363
title: Review Changes in GitHub
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_work_item_change_request.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_change_request.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 14716b346e1fdcf1db942b2ce262aa16bacc92cf799c8679d73319dff62197a3
description: Create a change request (pull request) so that a team member can review and approve your changes.
products:
  - Salesforce Platform
release: "264"
---
# Review Changes in GitHub

Create a change request (pull request) so that a team member can review and approve your changes.

`main`.

1. From the work item, click **Create Review** to move the work item to In Review.
    
    DevOps Center creates a change request and automatically opens a pull request for the changes in your work item branch.
2. (Optional) Click View Change Request to open a browser tab showing the pull request in GitHub, where reviewers can see the file changes.
    
    You can identify that DevOps Center created the change request by the subject line (1) and auto-generated comment (2).
    
    ![Pull request in GitHub with DevOps Center in subject line and comment that indicates DevOps Center created it.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/view-change-request.png)
3. Team members can add comments and have discussion in the pull request about the changes.
4. Go back to DevOps Center.
    
    What you do next depends on whether you merged the pull request in GitHub.
    
    - If you didn’t merge the pull request, indicate that the work item is ready to promote.
    - If you merged the pull request, the work item status is updated to **Ready to Promote**. The next step is to complete the promotion in DevOps Center or using Salesforce CLI.

To improve release quality, we recommend you set up and use [DevOps Testing](https://help.salesforce.com/s/articleView?id=platform.devops_testing_improve_release_quality_with_devops_testing.htm&language=en_US).

#### See Also

- [Indicate That Work Items Are Ready to Promote](https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_ready_to_promote.htm&release=264.0.0&type=5 "After the work item is reviewed, a team member approves the work item to be ready to promote. Work items aren’t available for promotion through the pipeline until they are in the Ready to Promote status.")
- [Promote Work Items Through Your Pipeline](https://help.salesforce.com/s/articleView?id=platform.devops_center_work_items_promote.htm&release=264.0.0&type=5 "You promote work items through a pipeline, which defines the sequence of stages that work items progress as they go through the release lifecycle from development to production (or some other final stage). You can have any number of pipeline stages. Your team manager built the pipeline when configuring DevOps Center.")