Yesterday we noticed something that might have been happening for a while, but it’s the first time we see it. When you change things in a quick succession on a Shopify theme connected to a GitHub connection, not all changes are properly propagated to our GitHub repository. We’ve waited a good while (almost a full day) in some cases and they never seem to come. We’re forced to pull the changes manually every time, just to make sure someone hasn’t touched the theme in that time. And there’s often leftovers.
I’ve also checked the logs, but I cannot see anything out of place in there, just your standard success logs:
03:13:06 PM: Received new theme files from Shopify
03:13:06 PM: Files fetched
03:13:06 PM: 1 succeeded, 0 warnings, 0 failed
03:13:06 PM: Theme updated!
Though, after doing a shopify theme pull, we see a few changes here and there.
Has anyone ever encountered something like this? I want to treat the repository as a source of truth and if I can’t trust it’s content, it gets concerning.
Hi,
Yes it’s happening something similar for us too.
We use github to make changes and let’s say we have edited 10 files, Shopify doesn’t sync all of them anymore but just part of them are reflected in the Shopify liquid code.
This is something that started happening recently, it used to work flawlessly before.
The service that handles the connection between Shopify and GitHub had a bit of a struggle this week processing all of the events GitHub was sending in a timely manner. This should be cleared up as of the last 10 minutes or so.
If this happens again in the future please let us know and we can dig into it to compare events we received and what you expected.
hey @Liam-Shopify I am encountering the issue. I made the changes in the github repo, but the changes haven’t synced to the theme in Shopify. Usually its instant but I’ve been waiting a while now and it hasn’t happened. Can you check to see if there’s an issue with this today or something? Thanks.
We are seeing the same on a production store, and it goes beyond newly added files.
Setup: live theme connected to a GitHub branch via the GitHub integration. The theme receives changes through the theme editor, Shopify CLI (shopify theme push --only ... --allow-live) and the Admin API (asset uploads). The integration keeps committing (“Update from Shopify for theme …”), the latest commit is from yesterday, so the connection itself is alive.
We compared a fresh full shopify theme pull of the live theme (770 files) with the connected branch at its latest commit:
~50 files exist only in the theme, not in the branch: all of them were added via CLI push or Admin API (e.g. a new section and about 50 SVG assets). Same pattern as reported above.
~35 files differ in content. Some examples:
one section file is 0 bytes in the branch but 2.6 KB in the theme
one snippet was last committed in February, a later fix pushed via CLI never arrived
several locales/*.schema.json, a CSS asset and customer templates are out of date
Nothing in the theme admin indicates that the branch is incomplete.
The practical risk: the branch cannot be used as a backup, and “Reset to last commit” would roll the live theme back to an incomplete state (empty section, missing assets). We now treat a full CLI pull as the only reliable backup.
Questions:
Is this the same root cause as the issue in this thread, or a separate one (existing files not updated / committed empty)?
Is there a way to force a full re-sync from theme to branch without disconnecting?
Is there an ETA or a recommended workaround?
Happy to share request IDs from the next CLI push if that helps the investigation.
we encounterred it again on some stores. 1 commit out of 3 does not go into shopify
