Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Enable Dev Hub Features in Your Org
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
See Changes Identified by Source Tracking
Pulling and Pushing Changes Identified by Source Tracking
Resolve Conflicts Between Your Local Project and Org
Get Change Information by Querying the SourceMember Object
Best Practices
Differences and Considerations
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Pulling and Pushing Changes Identified by Source Tracking

When working with source tracking, pulling and pushing changes only pulls or pushes added, changed, or deleted source.

Say you run force:source:status and see local and remote changes.

1=== Source Status
2STATE                     FULL NAME      TYPE              PROJECT PATH
3─────────────             ─────────      ─────────         ───────────────────────────────────────────────────────────────────────────
4Local  Add                WidgetClass       ApexClass      /WidgetClass.cls-meta.xml
5Local  Add                WidgetClass       ApexClass      /WidgetClass.cls
6Remote Changed            Widget__c         CustomObject   force-app/main/default/objects/Widget__c/Widget__c.object-meta.xml
7Remote Deleted            Widget__c.all     ListView       force-app/main/default/objects/Widget__c/listViews/All.listView-meta.xml
8Remote Add                WidgetPermissions PermissionSet

As a best practice, pull changes and resolve conflicts before pushing your changes to the org. This practice helps other developers incorporate your changes and generally facilitates collaboration. For help resolving conflicts, see Resolve Conflicts Between Your Local Project and Org.

1sfdx force:source:pull -u DevSandbox

After pulling source, run force:source:status again. Now, source tracking only reports your local changes because pulling updated your local project to match what’s in the org.

1=== Source Status
2STATE                     FULL NAME      TYPE            PROJECT PATH
3──────────                ───────────    ─────────       ─────────────────────────────
4Local  Add                WidgetClass    ApexClass       /WidgetClass.cls-meta.xml
5Local  Add                WidgetClass    ApexClass       /WidgetClass.cls

Next, push your local changes. After pushing, other developers see your changes in the org as remote changes.

1sfdx force:source:push -u DevSandbox

Run source tracking again.

1=== Source Status
2No results found

Source tracking reports no results, indicating that your local project and the org are synchronized.