bisnow/Storyblok dev → prod sync

Promote the Storyblok components, assets and stories named in .storyblok_sync/*.json from a dev space to a prod space, remapping every cross-space reference via the Management API.

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
dev-space-idSource (dev) space id.yes
prod-space-idTarget (prod) space id.yes
regionStoryblok region for both spaces (eu | us | ca | ap | cn).nous
dev-tokenPersonal access token with read access to the dev space.yes
prod-tokenPersonal access token with write access to the prod space (may equal dev-token).yes
sync-dirDirectory in the consumer repo holding the *.json sync files.no.storyblok_sync
dry-runWhen true, log the planned writes without calling the API.nofalse
update-storiesAfter assets change, repair asset references in existing prod stories not in this sync set.notrue
prune-presetsDelete stale presets of a synced component that no longer exist in dev.notrue
fail-on-partialExit non-zero when some (but not all) items fail.notrue
debugForce-visible debug logging, including every MAPI call. Also auto-on under GitHub step-debug.nofalse
clear-processed-filesDelete each sync file whose items all succeeded from the working tree (the workflow commits the deletions).nofalse
namedescription
components-syncedNumber of components created or updated.
assets-syncedNumber of assets created or updated.
stories-syncedNumber of stories created or updated.
summaryHuman-readable one-line summary of the run.
cleared-filesComma-separated list of sync files the action deleted (for the workflow to commit).