Updating codebase
Use this guide if you want to keep your project in sync with future ExpoLaunch releases. There are two main ways to keep your project in sync with future ExpoLaunch updates. Choose the one that best fits your level of customization.
Option A — Safe Manual Update Workflow (recommended)
Best for customized apps
If you plan to significantly modify the template, manual updates are safer and usually faster than resolving git conflicts.
How it works:
- Keep a clean clone of the template for reference:
git clone git@github.com:nativelaunch/expolaunch-template.git expolaunch-template- Build your app in a separate repo (or from the ZIP archive):
git init my-app
cd my-app
git remote add origin git@github.com:{your-username}/{your-repo}.git-
When a new release is available:
- Update your clean clone with
git pull - Review differences (configs, scripts, features)
- Manually copy or re-implement the parts you need
- Update your clean clone with
-
Test locally and commit changes with a clear message:
git commit -m "chore: apply updates from template v1.3.0"This approach avoids merge conflicts and keeps you in full control of what enters your codebase.
Option B — Track via upstream (advanced)
Best for minimal customization
If you keep your project close to the original template, you can track updates directly via upstream.
Setup (one time):
If you cloned our template repo and want your own origin:
git remote rename origin upstream
git remote add origin git@github.com:{your-username}/{your-repo}.git
git push -u origin mainIf you already have your own origin, just add upstream:
git remote add upstream git@github.com:nativelaunch/expolaunch-template.gitPull updates later:
git fetch upstream
git checkout -b update/from-upstream
git merge upstream/main # or: git rebase upstream/main
git push origin update/from-upstreamHeads up
Pulling upstream into a customized app can cause merge conflicts. Always review changes and test before merging.
FAQ
-
Which option should I choose?
- Heavy customization → Option A (manual)
- Light customization → Option B (upstream)
-
What if I started from the ZIP archive? Create your own repo, then either:
- Follow Option A with a clean clone for reference
- Or add the template as
upstreamfor direct sync
-
Merge or rebase?
- Both are fine.
mergeis simpler,rebasekeeps history linear. Pick what your team prefers.
- Both are fine.