---
schema_version: "1"
id: 3e10cb1bd595361fb206564902f777b2e286b4e2d065955f41920fba870544fb
title: Pull Changes from the Development Environment
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_pull_changes.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_pull_changes.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 967c714d5e7e80dd62896a19352b9047452055d5f7121e4b0a776c049d06a98a
description: Because the development environment has source tracking enabled, DevOps Center knows what files have been added, changed, or removed. When you pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository.
products:
  - Salesforce Platform
release: "264"
---
# Pull Changes from the Development Environment

Because the development environment has source tracking enabled, DevOps Center knows what files have been added, changed, or removed. When you pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository.

1. From within the Work Item Changes tab, click **Pull Changes**.
    
    DevOps Center displays how many files were pulled, how many files are available to pull, and how many files were ignored. See [Available Changes List](https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_available_changes_list.htm&release=264.0.0&type=5 "When you connect a source-tracked development environment to a work item and pull changes, DevOps Center displays a list of all files that it has identified as changed. These changes aren’t associated with the work item until you select and commit them to the source control repository. After a change is committed, it no longer appears in the Available Changes list.") for details. DevOps Center can retrieve approximately 40 changes at a time. You can keep clicking **Pull Changes** until all changes are listed.
2. (Optional) Click **n files ignored** to view which files were excluded as determined by the .forceignore file.
    
    In this example, two profiles were excluded and aren’t available to commit.
    
    ![Ignored Files dialog, which lists the excluded files and provides a hotlink to the .forceignore file in the project repository.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-devops_center-264-0-0-production-enus/166010c3-4c34-4087-92ad-aea917baf524/devops_center/images/ignored-files-dialog.png)
3. Next, [select the changes to commit](https://help.salesforce.com/s/articleView?id=platform.devops_center_work_item_commit_changes.htm&release=264.0.0&type=5 "After you decide which changes to include for the work item, commit the changes to the project’s source control repository. When you commit changes, they’re stored in the repository branch that was created when the work item moved to the In Progress stage.") to the source control repository.

#### See Also

- [_Metadata API Guide_: Deleting Components from an Organization](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_deploy_deleting_files.htm)