project reset tracking

Reset local and remote source tracking.

Description for project reset tracking 

WARNING: This command deletes or overwrites all existing source tracking files. Use with extreme caution.

Resets local and remote source tracking so that Salesforce CLI no longer registers differences between your local files and those in the org. When you next run ‘project deploy preview’, Salesforce CLI returns no results, even though conflicts might actually exist. Salesforce CLI then resumes tracking new source changes as usual.

Use the –revision flag to reset source tracking to a specific revision number of an org source member. To get the revision number, query the SourceMember Tooling API object with the ‘data soql’ command. For example:

sf data query –query “SELECT MemberName, MemberType, RevisionCounter FROM SourceMember” –use-tooling-api –target-org my-scratch

Aliases for project reset tracking 

force:source:tracking:reset

Flags 

Flag Name (Long)Flag Name (Short)Description
‑‑api‑versionN/AType: Value

Override the api version used for api requests made by this command
‑‑flags‑dirN/AType: Value

Import flag values from a directory.
‑‑jsonN/AType: Boolean

Format output as json.
‑‑no‑prompt‑pType: Boolean

Don’t prompt for source tracking override confirmation.
‑‑revision‑rType: Value

SourceMember revision counter number to reset to.
‑‑target‑org‑oType: Value
Required

Username or alias of the target org. Not required if the target-org configuration variable is already set.

Examples for project reset tracking 

Reset source tracking for the org with alias “my-scratch”:

1sf project reset tracking --target-org my-scratch

Reset source tracking to revision number 30 for your default org:

1sf project reset tracking --revision 30