Change Management

1. What is it?
A feature that tracks the changes Blaze makes, so you can review them and roll them back to an earlier state.
When you let the AI handle many Salesforce metadata files at once, you eventually hit moments like “what actually changed?” or “I don’t like this, take me back.” Change Management makes changes across your workspace visible per file, and lets you save them as records and revert to an earlier state.
- Automatically tracks the files Blaze edits
- Lets you view the diff right there
- Lets you roll back to an earlier point in time
- Lets you send your saved changes to the repository you push to and share them with your team
2. Get started
- Connect to a Salesforce org.
- Open Changes from the left sidebar.
- Choose Start Change Management to record local changes, or Connect a repository to start with your team’s repository.
These choices appear when Change Management has not been started for the org. To use a team repository, follow Connect to a team repository.

3. Reading the screen
“Changes” is made up of three main areas.
| Area | What it shows |
|---|---|
| Ready to Save | Changes you have selected to record |
| Unsaved Files | Changes you have not saved yet |
| History | The list of records you have saved over time |
Press ”⋯” below “Save Changes” to push and pull, check your Salesforce org for changes, and change view settings.
4. What you can do
| What you want to do | Article |
|---|---|
| Connect to a team repository and choose a branch | Connect to a team repository |
| Choose changes and record the current state | Save changes |
| Return your files and org to a saved point | Revert to an earlier version |
| Compare local content with Salesforce and bring in selected content | Check differences with Salesforce |
| Send your saved changes to the repository you push to | Push changes |
| Bring changes in the repository you push to into this computer | Pull changes |
| Change which files appear in the list | Show changes to non-metadata files |
| Exclude logs and temporary files from change management | Choose files whose changes will not be saved |
5. FAQ
Q. Do I need to install Git?
No. Everything Change Management needs is bundled with Blaze. It works out of the box with nothing to install.
Q. Are any files left out of Change Management?
Yes. Untracked files excluded by .gitignore and embedded Git repositories in the workspace are left out. See Choose files whose changes will not be saved for the settings and how already tracked files are handled.
Q. Some files don’t appear under Change Management on Windows
Windows does not allow reserved names such as CON or NUL as file names. Files with such names are automatically excluded from Change Management to avoid problems.