Create delta package.xml from between two branches of Github

Install

npm install -g sfdx-delta-package

Usage

sfdx-delta-package -sb develop -tb master

Options

  -V, --version                 output the version number
  -f, --file <type>             Delta file path
  -sb, --source-branch <type>   Source Branch of Git
  -tb, --target-branch <type>   Target Branch of Git
  -v, --package-version <type>  Package.xml version (default: "60.0")
  -o, --output-path <type>      Output path (default: "manifest/package.xml")
  -l, --local-git               Check changes in local git
  -display, --display-output    Display package.xml as an console output
  -d, --destructive-changes     To Create destructiveChanges.xml file for deleted files under destructive folder.
  -h, --help                    display help for command

Examples

  To get help:
    $ sfdx-delta-package --help
    $ sfdx-delta-package -h

  Generate package.xml with delta file:
    $ sfdx-delta-package -f file_path.txt

  Generate package.xml from source and target branch of GitHub:
    $ sfdx-delta-package -sb source_branch -tb target_branch
  
  Generate package.xml from source and target branch of GitHub with package.xml version as 57.0:
    $ sfdx-delta-package -sb source_branch -tb target_branch -v 57.0

  Generate package.xml from local source and target branch of Git branches:
    $ sfdx-delta-package -sb source_branch -tb target_branch -l

  Generate package.xml from delta file and store in different directory or folder:
    $ sfdx-delta-package -f file_path.txt -o main/profiles.xml
  
  Generate package.xml and destructiveChanges.xml for deleted files and store in destructive folder:
    $ sfdx-delta-package -sb source_branch -tb target_branch -v 60.0 -d

Note

We can update the metadata coverage using metadata.js file. For full support on Salesforce metadata use this metadata coverage report.