Getting kit updates
Pull fixes and new features from Launchfast into your product without losing your changes.
If you followed the Quickstart, your project has two Git remotes:
origin: your own repositorylaunchkit: the Launchfast repository
Check with git remote -v. If launchkit is missing, add it:
git remote add launchkit https://github.com/launchfast-today/launchkit.gitPull updates
git checkout main
git pull launchkit mainGit merges the kit's new commits into yours. Then:
npm install # in case dependencies changed
npm run db:migrate # in case there are new migrations
npm run typecheck && npm test && npm run build
git pushConflicts
You'll get conflicts in files both you and the kit changed, most often src/config.ts, src/content/landing.ts, src/app/globals.css, .env.example and README.md.
- For your content files (
landing.ts,config.ts, the legal pages), keep your version and copy in any new fields the kit added. - For kit code you haven't touched, take theirs:
git checkout --theirs <file>. - Ask your AI agent: "Resolve the merge conflicts from pulling launchkit, keeping my product's content and the kit's code changes."
When done: git add -A && git commit.
Fewer conflicts
Keep your product's own code in new files and folders (for example src/app/dashboard/projects/) rather than editing kit files where you can. Updates then rarely touch your code.
"refusing to merge unrelated histories"
Your repository was created from a copy of the files rather than a clone, so Git sees no shared history. Run the first pull with:
git pull launchkit main --allow-unrelated-historiesExpect conflicts in most files the first time.