Skip to content
OpenStock
OpenStock

Get started

Theme CLIInstall and sign in

Workflow

Develop a themeSyncing and conflictsCI and automation

Reference

Commands
Dashboard
  1. CLI
  2. Workflow

Syncing and conflicts

How push and pull track changes and protect edits made in the dashboard.

The CLI remembers the content of every file as of your last pull or push. That lets it tell your edits apart from edits made elsewhere, such as in the dashboard code editor or by a teammate.

Push#

openstock push uploads files you changed or added and deletes files you removed. Before it writes anything it checks the server: if a file you changed was also changed there, the push stops and lists the files so nothing is overwritten by accident.

$ openstock push
  ! 1 file changed on the server since your last sync:
    src/styles.css

  ✗ Push stopped so nothing gets overwritten.
  Run `openstock pull` to merge, or `openstock push --force` to overwrite.

Pull#

openstock pull brings down server changes. Files you have edited locally are left alone and reported, so pulling never destroys work. Use --force to take the server version of everything.

Status#

openstock status lists what a push would send, without contacting the server.

What gets synced#

  • Files ending in .tsx .ts .jsx .js .css .json .html .md .svg .txt, up to 512 KB each.
  • Skipped: node_modules, dotfiles and folders, dist, build, lockfiles, openstock.json and the generated src/data/store.json.

Images belong in your store’s media library or a CDN; reference them by URL.

Was this page helpful?

PreviousDevelop a themeNextCI and automation
© 2026 OpenStockTermsPrivacy