GitHub · Theme versioning & handover
A traceable history when more than one person touches the theme.
FREE → PAID
Why I use it
- Rollback and diff views in a few clicks.
- Pull requests to validate changes with the client or another dev.
How I use it : mini guide
Private repo per client or mono-repo with an agreed folder convention at kickoff.
- Branches : main/production vs feature branches for isolated work.
- Commits : Descriptive messages : easier handover and post-mortems.
- Releases : Tags on major production releases to snapshot state.
- Access : Invite client read or write depending on maturity.
Secrets (.env, tokens) never get committed : strict .gitignore + Shopify env vars.
Concrete Shopify example
Post app update regression: revert to last tagged release, patch, redeploy.
Limits I've identified
- Learning curve for non-dev teams.
- Merge conflicts on messy Liquid cost time.
- Organisational overhead on tiny fixes.