https://github.com/dlively1/sf-packager
Salesforce.com package builder using git diff
https://github.com/dlively1/sf-packager
forcedotcom git-diff salesforce
Last synced: 2 months ago
JSON representation
Salesforce.com package builder using git diff
- Host: GitHub
- URL: https://github.com/dlively1/sf-packager
- Owner: dlively1
- License: mit
- Created: 2016-01-21T03:19:45.000Z (about 10 years ago)
- Default Branch: master
- Last Pushed: 2023-06-19T08:56:44.000Z (almost 3 years ago)
- Last Synced: 2025-10-28T16:38:25.425Z (5 months ago)
- Topics: forcedotcom, git-diff, salesforce
- Language: JavaScript
- Size: 128 KB
- Stars: 41
- Watchers: 5
- Forks: 35
- Open Issues: 4
-
Metadata Files:
- Readme: readme.md
- Funding: FUNDING.yml
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Overview
CLI Tool to generate Salesforce.com package.xml (and destructiveChange.xml) files based on git diff between two branches, commits, or tags.
## Install
```
npm install -g sf-packager
```
## Usage
```
$ sfpackage destinationBranch sourceBranch ./deploy/
```
This will create a package at ./deploy/sourceBranch/unpackaged/package.xml copying all files into directory.
If any deletes occurred will also create ./deploy/sourceBranch/destructive/destructiveChanges.xml
You can force a specific version for the package.xml with the -p flag
```
sfpackage destinationBranch sourceBranch -p 42 ./deploy/
```
You can also just write the package.xml and destructiveChanges.xml by passing the -d flag
```
sfpackage destinationBranch sourceBranch -d > ~/Desktop/packageAndDestructiveChanges.xml
```
You can also create "backout" content by reversing the order of the destination and source branches
```
sfpackage sourceBranch destinationBranch ./deploy/
```