GitHub integration ignores new files added via `shopify theme push`

Online Store and Theme Development
,
1

Short description of issue

When using shopify theme push with a theme connected to GitHub, newly added files are missing from the commit created by the GitHub integration. Only changes to files that were already tracked appear to be committed.

Reproduction steps

  1. Connect a Shopify theme to a GitHub repository/branch using the Shopify GitHub integration.

  2. Make changes locally to the theme:

    • Modify an existing tracked file.
    • Add a new file, for example:
      snippets/new-snippet.liquid

  3. Push the theme using:
    shopify theme push

  4. Wait for the Shopify GitHub integration to create/sync the corresponding commit.

  5. Inspect the commit created by the GitHub integration.

  6. The modification to the existing file is included, but the newly created file is missing.

Additional info

Expected behavior:
All files uploaded by shopify theme push, including newly created files, should be included in the commit produced by the GitHub integration.

Actual behavior:
The GitHub integration appears to only commit modifications to files that were already tracked. Newly created files uploaded as part of the same shopify theme push are ignored.

Example:
If I modify sections/product.liquid and create a new file called snippets/new-snippet.liquid, both files are pushed to the Shopify theme.

However, the commit generated by the GitHub integration contains the modification to sections/product.liquid but does not contain snippets/new-snippet.liquid.

Impact:
This can result in broken or incomplete themes when the generated commit is later merged into another branch. Existing files may reference newly added snippets/assets/templates that are absent from Git, even though they were part of the original theme push.

What type of topic is this

Bug report

2

Hey @Piotr_Joniec - thanks for flagging this.

Could you run shopify theme push --verbose to reproduce the issue and share all the x-request-id values from the output? Please share only those IDs, since the full verbose output can contain sensitive data. This should let us trace the upload requests and the downstream GitHub sync to better understand what happened here.

3

Here are the request IDs from a reproduction. In this specific case, the modifications to blocks/_media_card.liquid weren’t included in the commit.

It turns out this bug is more complicated than a simple case of new files not being included in the commit. I can’t tell what’s causing it, and I don’t even know why it’s blocks/_media_card.liquid this time.

eab83388-6938-4a9a-a9ac-11abf3d0c014-1788548066
f3abb411-088a-43d0-b020-0c3fbbbdcbf4-1788548066
972fd7bf-5483-4b45-ba7f-5c89a00711b9-1788548074
f75b78df-d66d-4dcd-a599-0c783ff3bb58-1788548074
65d9b14b-d165-459f-9a70-33e945a02908-1788548074
2800d58a-aee1-4b4d-932b-61ba4f35b3cd-1788548074
84b0dc64-1387-4fa2-bfa7-ec0874d4c032-1788548075
215ab3bd-1cf6-4f0e-8181-aef239160985-1788548076
825f89a9-c22d-4a47-86a9-3e648596962a-1788548075
5f823fe5-23ab-4e15-aa96-57e163738490-1788548077
5

Hey @Piotr_Joniec - thanks for sending those through. That’s very helpful.

I’m digging into this now and will follow up here as soon as I have an update.

6

@Wes-Dev-Shopify any news on this?

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 store 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:

  1. Is this the same root cause as the issue in this thread, or a separate one (existing files not updated / committed empty)?
  2. Is there a way to force a full re-sync from theme to branch without disconnecting?
  3. Is there an ETA or a recommended workaround?

Happy to share request IDs from the next CLI push if that helps the investigation.

7

Hey @Ray - thanks for sharing these details. We’re still looking into this and don’t have an update to share yet.

Some more examples could definitely help with our investigation. Could you add --verbose to your next shopify theme push that reproduces the issue and share all the x-request-id values from that run? Please share only the IDs, since the full verbose output can contain sensitive data.

I’ll continue to update this thread as soon as I have more to share.