Git Integration
Connect any HTTPS git repository. ThemeSync clones it, pulls changes automatically, and — for production themes — commits changes from Shopify back to git.
Overview
Git is optional but recommended. Without it, ThemeSync still runs a dev server and takes QA screenshots — git just adds the ability to auto-pull code changes and maintain a version history of your theme.
Connecting a Repo
Add a git URL when creating a theme or in Theme Settings → Git.
- Supports GitHub, GitLab, Bitbucket, and any self-hosted HTTPS git server
- Private repos: provide a Personal Access Token or App Password
- Each theme gets its own isolated working copy of the repo
- Credentials are encrypted at rest — not displayed after saving
Token setup by provider
| Provider | Token type | Required permissions |
|---|---|---|
| GitHub | Personal Access Token (classic or fine-grained) | Contents: Read & Write |
| GitLab | Project or Personal Access Token | read_repository, write_repository |
| Bitbucket | App Password | Repositories: Read, Write |
Auto-Sync
Auto-sync behaviour depends on the theme type:
| Theme type | Direction | What happens |
|---|---|---|
| Development | Remote git → workdir | Pulls latest commits; triggers live-reload in the dev server |
| Production | Shopify → git | Pulls live theme from Shopify, commits and pushes to your repo |
| WooCommerce | Remote git → WP site | Pulls latest commits; deploys theme files to WordPress |
Sync intervals
| Interval | Best for |
|---|---|
| Off | Manual control only |
| 30 seconds | Active development — near-instant updates |
| 1 minute | Default — good balance |
| 5 minutes | Low-activity branches, staging |
Manual sync is always available via Pull in the Git Changes modal or the Git Source card on the Overview tab.
Branches & Versions
To preview a different branch, use Duplicate Version from the theme action menu (⋮):
- Open the action menu on any theme card
- Click Duplicate Version
- Choose a different git branch
- Optionally carry over template mappings from the source theme
- Both themes run simultaneously — compare preview URLs side-by-side
Common use cases: A/B testing designs, reviewing a feature branch before merging, running a "staging" and "main" preview in parallel for a client presentation.