Skip to main content
All CollectionsHelp ArticlesMetadata Deployment
Commit to GIT - Source Format Selection Options
Commit to GIT - Source Format Selection Options

How to select Salesforce DX as your source format file structure using Copado Essentials Plus.

T
Written by Tam Tran
Updated over a week ago

With Copado Essentials' source format selection picklist option, you can choose the format of the source to be stored in Git. This article explains each of the options available in this picklist.

GITSourceFormat.png

Auto Detect

If the repository is new: the default format is Metadata API. A default package.xml will be created and committed to the repository. All changes will be committed to GIT in Metadata format

If the repository is not new and already has source code: Copado Essentials will try to detect the source format by parsing the repository.

  • If the package.xml file exists in the repository – Metadata format will be used

  • If a sfdx-project.json file exists in the repository – Salesforce DX format will be used

  • If both package.xml and sfdx-project.json are not available, Copado Essentials will treat the repository as new and create a new package.xml

Metadata API option:

All changes will be committed to GIT in Metadata format

If package.xml file doesn't exist, a default package.xml will be created and committed to GIT.

Salesforce DX option:

All changes will be committed to GIT in DX format

If sfdx-project.json file doesn't exist, a default sfdx-project.json will be created and committed to GIT.

Did this answer your question?