Salesforce DX Metadata Format

Modern DevOps workflows rely on Salesforce DX (SFDX) to treat org configuration like code. Instead of a monolithic ZIP, your metadata lives in a source-tracked directory structure that maps cleanly to Git and CI/CD pipelines. AutoRABIT embraces this model and adds automation on top—but it needs to know which folder(s) contain your DX-formatted source.

---

Overview

AutoRABIT identifies an SFDX repository by locating an sfdx-project.json file in the root:

This file includes a packageDirectories array. Each entry defines a Package Directory—the root of your metadata for pushes to and pulls from scratch orgs.

If you register an existing DX repo with AutoRABIT, ensure every source folder is listed under packageDirectories. Click Refresh in the UI if the directories don’t appear immediately.

Supported layout AutoRABIT currently supports the standard DX structure only: <package-directory>/main/default/* (Created automatically by sfdx force:project:create.)

You may declare multiple package directories, but each must follow the same /main/default sub-tree.

---

Places to Select the Source SFDX Folder

EZ-Commit Screen

Choose Package Directory when committing metadata from a Salesforce org to an SFDX branch.

During a CI Job

Select the folder while deploying SFDX source from Version Control to a Salesforce org.

Branching Baseline Operation

When committing all metadata from a Salesforce org into an SFDX branch, pick the directory here.

Creating Unlocked/Managed Packages

Specify Package Directory while defining an unlocked or managed package.

New Commit Labels

Commit labels for DX repos also require the source folder.

Release Label Creation

Choose the directory again when generating a release label.