ReleaseWPChangeSync 2.0 is here →
Guides/Git Version Control Workflow

Git Version Control Workflow

Store WPChangeSync JSON exports in Git so builder and content changes are reviewable.
Updated 5 June 2026·Task guide

Outcome

Builder templates, components, settings, and selected integration data are exported into Git-friendly JSON files that can be reviewed, committed, and deployed with the rest of your project.

Video walkthrough

▶

Video walkthrough coming soon.

The YouTube embed will appear here.
Risk level

Medium. Exporting is safe; imports from Git-tracked JSON need dry runs and review.

Before you start

  • Use a storage folder inside or next to the active theme if you want Git to track exports.
  • Decide which integrations belong in source control.
  • Keep credentials, tokens, remotes, and secrets out of committed JSON.

Steps

  1. Set storage to a Git-tracked folder
    In Config -> Storage, point exports to a folder your repository tracks.
  2. Create an Export to Storage workflow
    Include templates, components, settings, global styles, fields, or other integrations that should be versioned.
  3. Export after meaningful changes
    Run the workflow after approved builder/content changes.
  4. Review the diff
    Check filenames, JSON changes, deleted items, and related-data moves.
  5. Commit with release intent
    Use commit messages that explain the user-facing change, not just “export”.

Screenshots

Set Storage to Theme Folder
Set Storage to Theme Folder
wp wpchangesync workflow run export-to-storage --mode=dry_runnwp wpchangesync workflow run export-to-storagengit statusngit add wpchangesync/ngit commit -m "Release updated header templates"
Git is not a backup by itself
A Git commit helps review and restore files, but imports should still create WPChangeSync backups before replacing WordPress data.

Verify and recover

After completing this guide, verify the result in Activity and on the target site. Keep the pre-change export or backup until the release has been accepted. If anything looks wrong, stop further syncs, restore the affected item or integration from backup, and re-run with a narrower scope or safer conflict strategy.

How to find the workflow ID

Open Workflows in the admin UI and inspect the workflow details, or run wp wpchangesync workflow list. Use the ID from that list in workflow show and workflow run commands.