Project archive
Shopify–GitHub theme pipeline
Multi-store CI/CD for Shopify themes that never overwrites a merchant's live edits.
- My role
- Creator and main author, about 70% of create-theme's 190 commits and 38 of ci-workflows' 50
- When
- April 2026 — present, at Prosper Digital
- Original
- Private Prosper Digital repositories
- Archived
A copy kept here in case the original moves, goes offline, or I lose access to it.
Shopify themes have two authors. Developers change code in Git; merchants change content, settings and templates in the theme editor, on the live theme. Shopify's own GitHub integration syncs one theme with one branch, and a careless deploy can overwrite a merchant's edits without anyone noticing. I built Prosper's pipeline so both kinds of work flow safely, across one store or a fleet of regional stores.
It has two parts, both private: create-theme, a CLI that sets up a theme repository, and ci-workflows, the shared GitHub Actions every theme repository calls.
create-theme
One command turns any Shopify theme, local or from Git, into a repository with Prosper's production setup: Vite, Tailwind v4, Biome, Lefthook and GitHub Actions. It pulls the live theme's data, can create the matching QA and release themes in Shopify, and vendors pd-components on request.
It also ships as a Claude plugin. Anyone at Prosper can ask Claude to set up a new client theme repository; the plugin checks their tools and logins, asks for the client, store, source theme and first release, runs the CLI, and walks them through connecting the themes in Shopify admin. No terminal knowledge needed.
The branch model
Each branch maps to a Shopify theme, and each regional store mirrors the same structure with a region prefix. main is the source of code and data; trunk/<release> collects a release.
Main store
maincanaryQA themetrunk/<release>rc/<release>Release theme, goes live
Each regional store
store-<region>canary-<region>QA themetrunk-<region>/…rc-<region>/…Release theme, goes live
Protecting live edits
Every build
Every day
Every theme file falls into one of five buckets: editor data, Liquid, hand-maintained assets, compiled Vite output, and build churn. The pipeline treats each differently:
- Every build lands on its theme through a data-guarded merge. Edits made only in the theme editor are kept; when a merchant and a developer changed the same editor data, the build stops instead of silently picking one.
- On a live release theme, the guard also covers Liquid and hand-maintained assets, and catches both-sided edits that Git would have merged cleanly without a conflict.
- A provenance check fails the build if any compiled asset on the live theme was last changed by someone other than CI.
- Pull requests predict conflicts with the QA and release themes before they merge.
- A scheduled job spots edits on a live theme since its last build and flags them on a standing pull request, which carries the merchant's editor data back to the release branch.
- Every live theme is tagged daily as a snapshot, kept for about 30 days.
Running releases
Creating a release cuts its branches for every store, opens a pull request per store and a release issue that tracks them, and runs the first build. Commenting /seal or /unseal on that issue freezes or reopens the release branches, and they seal themselves after 14 days with no code changes. One workflow applies a fix to every store's release branch at once, skipping sealed ones and reporting each store's status on the issue. Slack hears about direct pushes to live themes.
When a client takes over their repository, the workflows can keep running on Prosper's CI server instead: it clones the repository in a Vercel Sandbox and runs the same job scripts there, so the client never receives the pipeline's code.