Automated Force.com project rollback with git integration. As of the initial 0.1.0 release, the destructivator CLI produces a
destructiveChanges.xml
file based on the deltas between a feature branch and master branch of a git repository.
git clone https://github.com/ancamcheachta/destructivator.git
cd destructivator
cargo install
Here's an example of how to generate destructiveChanges.xml
from the diff between a feature and master branch of a Force.com project.
git clone https://github.com/ancamcheachta/forcedotcom-project -b feature
cd forcedotcom-project
destructivator > destructiveChanges.xml
- Support for components in nested directories whose parent directory is not that of the component (eg. descendants of
/documents
) - Support for components with a many-to-one relationship to their parent folder (eg.
StandardObject
,CustomObject
to/objects
) - Rollback branch generator
- Expose public functions via
libdestructivator.so
- atom.io plugin