Rollouts - where is this content / config saved?

Theme Store
1

Hi

We have merchants using the great new Rollout feature - and one currently has one active Rollout.

My question is where does this configuration / content data reside please? We have our Git Repo connected to the published themes and I need to understand how not to overwrite their changes, and also how best to save their Rollouts into our version control.

Any guidance would be much appreciated.

Thanks

2

Hey @Jonathan_Davies - thanks for flagging! Happy to dig into this, just wondering if could you clarify the below before I do though:

  1. When you say the Rollout is active, is it currently running, or created/scheduled but not started?
  2. What type of theme content or settings does it change?
  3. After saving or activating the Rollout, did a new automatic commit from Shopify appear in the connected GitHub branch? If so, which files changed?

If possible, the store domain, theme ID, Rollout ID/name would be super helpful as well. Let me know if you’d rather set up a DM for that and I can handle that on my side. That’ll help us compare the Rollout state with the theme files and Git history.

3

Hi Alan,

Thank you for you response.

  1. Yes it is running
  2. It hides one section and reveals another on the default product template.
  3. There is no automatic commit when the rollout is active - but it does record the change once the test completes and is successful - which makes sense

It just means we have a detachment from the tests and the live theme, that we need to be aware of - whilst they are live.

4

Hey @Jonathan_Davies - thanks for confirming. I looked into this a bit more, and what we’re seeing here is actually expected for this type of Rollout.

While it’s active, Shopify stores the treatment as an override layer on top of the published theme. It isn’t written to the connected GitHub branch as a normal theme-file change, which is why there’s no commit during the test.

If the merchant decides to apply the treatment, those changes are merged into the published theme and the GitHub integration should then create its usual commit.

If the treatment is discarded, there’s no corresponding theme change to commit.
There isn’t currently a supported way to save the active Rollout itself in Git. For this specific case, I’d avoid changing the affected default product template while the test is running. Once the merchant applies the treatment, you can pull the Shopify-generated commit and review the resulting templates/product.json diff before continuing development.

For an audit trail before then, you could record the Rollout name, dates, and intended section changes in a ticket or non-deploying branch. Let me know if I can clarify anything on our end here - happy to pass along any feature requests you’d think could make this better too. Can’t guarantee anything there, but happy to pass along any requests for sure.

5

Thank you very much - good to get an understanding of how it works, so we can adjust our workflow accordingly. Much appreciated.