Skip to main content
The Theme Deployments tab displays all theme deployments committed to GitHub and awaiting approval before being deployed to a Shopify environment. It is the controlled promotion path from a developer commit through preview, approval, and final upload to a Shopify storefront. You must connect your GitHub repository under Settings, Connect Repository before you can use this function. See GitHub deployment for the connection steps.

​
The deployment queue

Theme deployments queue The queue lists every commit pushed to your connected Vortex Staging branches awaiting approval. Each row shows the commit message, the developer who pushed, the target environment, and the current state.

​
Approving a deployment

After the deployment is approved, the app starts building the theme files. Once the theme files are successfully built, the download link for the theme is enabled. Approved deployment building theme files Theme files built and download enabled

​
Uploading to Shopify

Upload the theme file you just downloaded using the Upload theme file option in the Shopify control panel. Upload theme to Shopify

​
Previewing the deploy

Click the Theme Preview option to view the updated theme file changes via a front-end URL preview. Theme preview link The modified text will be displayed on the home page in the theme’s preview URL. Theme preview rendered

​
Deployment status scenarios

The Theme Deployments grid surfaces four primary states:

​
Awaiting Approval

  • The Git commit appears in the grid.
  • Approval is required before merge.
Available actions:
  • Approve and Deploy. Deploy immediately.
  • Generate Preview and Approve Later. Preview changes before approval. Select the compatible Node.js version, click Launch, and the preview URL is generated within up to 5 minutes.

​
Approved and Deployed

  • Status: Merge Successful, Theme Deployed.
  • Code is merged into the respective environment branch.
  • Deployment may take 15-20 minutes depending on theme size as Vortex Staging builds the theme bundle and uploads it to Shopify.
  • A Rollback option is available to revert to a previous version.

​
Errors or Conflicts

  • Conflicts (for example, in config.json) are detected.
  • Click to view and resolve conflicts before proceeding.
  • Click Reject to cancel deployment.

​
Rejected

  • Status: Rejected, Code Not Approved.
  • No changes are merged into the environment.

​
Rolling back a theme deployment

Every approved and deployed commit is available as a rollback option in the deployment grid. To roll back:
  1. Find the previous good commit in the grid.
  2. Click Rollback.
  3. Vortex Staging rebuilds the theme bundle from that commit.
  4. Upload the rolled-back bundle to Shopify (or it is auto-uploaded depending on your environment settings).
This is the safety net for a deploy that broke something on the storefront. The rollback always references a real commit in your GitHub history, so you have a complete audit trail.

​
Why GitHub is required

Theme deployments via the Theme Deployments tab require GitHub because the workflow is commit-based. Each deploy maps to a specific Git commit, which means:
  • Every deploy has a permanent audit record.
  • Rollbacks reference real commits with a real diff.
  • Multiple developers can work on the same theme in branches without stepping on each other.
  • CI hooks and pre-deploy checks (linting, build validation) run automatically before approval.
If you only want to migrate a theme as part of a bulk migration (without going through the GitHub-approved deployment workflow), use the bulk migration Themes entity in Bulk content migration. That path is suitable for “copy this theme from production to staging” use cases.

​
FAQ

​
Why does preview generation take up to 5 minutes?

The time required to generate a preview URL depends on the size of the theme files. The process involves provisioning a temporary server and installing the theme.

​
Why does deployment take 15-20 minutes after approval?

After approval, deployment may take 15-20 minutes depending on theme size. This time is required to create the theme bundle and upload it to Shopify.

​
Can I deploy directly to Production without approval?

The recommended workflow is to approve in a non-production environment first, then promote. For genuine hotfix scenarios, you can commit directly to the Production branch. See GitHub deployment for the hotfix workflow diagram.

​
Do GitHub commits appear as rollback options?

Yes. All tracked commits appear as rollback options in the deployment grid.