Loading...
Your purchase includes lifetime updates. As FastStaq improves, you can pull those changes into your own copy. This guide shows a safe workflow that keeps your customizations intact.
Treat the FastStaq repository as an upstream you pull from, and keep your work on your own branches.
When you first set up your project, add the FastStaq repo as a second remote (commonly called upstream):
git remote add upstream <faststaq-repo-url>
git remote -v
Your own fork or repository stays as origin.
git fetch upstream
git log --oneline HEAD..upstream/main
This shows what changed before you merge anything.
Always merge into a dedicated branch first, never straight onto your production branch:
git checkout -b chore/faststaq-update
git merge upstream/main
If you have customized files that also changed upstream, Git will flag conflicts. Resolve them file by file, keeping your product logic while adopting upstream fixes. Run the app and the tests after resolving.
pnpm install
pnpm --filter @faststaq/server db:migrate:deploy
pnpm test
Once everything passes, merge chore/faststaq-update into your main branch.
Open a support ticket if a merge leaves you stuck.
Sign in to leave feedback on this article.