GitHub
GitHub integration
GitHub holds the code for every store we build. The Shopify GitHub integration means theme changes are reviewed, versioned and reversible.
UPDATED OCT 2026 · SOURCES (4)
GITHUB INTEGRATION AT A GLANCE
COMPLEXITY
Low
METHOD
TYPICAL SETUP
1 day
WHAT WE DO
Connect the theme to a GitHub repo, set up branches for staging and production, protect main, and run checks before anything goes live.
CATEGORY
Design & dev
SETUP BY PLATFORM
How we set up GitHub
Shopify
GitHub on Shopify (GitHub integration): Connect the theme to a GitHub repo, set up branches for staging and production, protect main, and run checks before anything goes live.
Shopify store builds →Shopify Plus
On Shopify Plus (GitHub integration): everything in Shopify, plus the Plus-only hooks (checkout extensions, B2B, Launchpad) where GitHub can use them.
Hydrogen
On a headless storefront (Hydrogen, Astro or Next.js) we connect GitHub through Native and own the event and data mapping ourselves.
USE CASES
What teams use it for
Theme version control
Every theme change in a pull request with a preview theme.
Staging workflow
Branch → staging theme → review → main → live.
Headless deploys
Astro, Hydrogen and Next.js storefronts deploy from GitHub to Vercel or Oxygen.
BEFORE YOU ADD IT
What to watch out for
EDITOR
Admin edits create commits
Changes in the theme editor commit back to the branch; keep settings and code separate.
PROTECTION
Protect main
Require reviews on main so nobody pushes straight to the live theme.
SECRETS
Never commit keys
API keys live in environment variables, not the repo.
05
GitHub in our process
Every theme and storefront we build lives in a GitHub repository the client owns. Shopify's GitHub integration connects a branch to a theme, so a merge deploys and the whole history of the store's code is reviewable.
We work on feature branches, open pull requests with a staging theme link and a Loom, and merge to the production branch only after the client has approved on staging. Theme Check and a small test suite run on every pull request. For headless builds the same repository holds the storefront and deploys to Vercel, Netlify or Oxygen on merge.
The point is ownership and continuity. If you change agencies, hire in-house or need an emergency fix at 2am, the code, the history and the deploy pipeline are yours, in your account, with our access revocable in one click. Stores that come to us with no repository — edits made in the theme editor for years — get one on day one, before anything else is touched.
Does Shopify integrate with GitHub?
Yes. Shopify's GitHub integration connects a branch to a theme, so a merge deploys and the whole history of the store's code is reviewable.
Who owns the repository?
You do. The repository lives in your account, with our access revocable in one click. Stores that arrive without a repository get one on day one.
Can our developers work in the repo?
Yes. Work happens on feature branches and pull requests with a staging theme link, and the code, history and deploy pipeline are yours. We protect main so nobody pushes straight to the live theme.
What about theme editor changes?
Changes in the theme editor commit back to the branch, so we keep settings and code separate. We also require reviews on main so nothing goes straight to the live theme.
You've reached the end, so now…
Tell us what you're selling.
Send us your store. Within one business day you get a short Loom from a senior: the three things we'd fix first, what it would cost, and whether we're the right team for it.
- No pitch deck, no discovery-call theatre
- You keep the audit whether or not you hire us
- Fixed-scope quotes, no hourly surprises
Prefer to talk? Book 20 minutes with Haniel or call +1 855-764-4977