GitHub Sync requires Team plan or higher. See Plans for details.
GitHub Sync connects your Chippy app to a GitHub repository. You can import existing code into Chippy for prototyping, or export your app to a repo for engineering handoff and review.
In the builder, go to your app’s GitHub Sync settings.
GitHub Sync settings in the builder
2
Connect your GitHub account
Click Connect GitHub. Authorize Chippy to access your repositories. You will only need to do this once.
Connecting your GitHub account
3
Select a repository and branch
Choose the repository you want to import from. Then select the branch (e.g., main, develop, or a feature branch).
Selecting a repository and branch
4
Import
Click Import. Chippy pulls the code from the selected branch into your app. The import may take a few moments depending on the size of the repository.
Import in progress
5
Review the imported code
Once the import completes, review the imported files in the builder. Verify that the code structure and files look correct before making changes.
Importing does not create a live sync. The import is a one-time snapshot of the repository at the selected branch. To get updates from the repo later, import again.
Export pushes your Chippy app to a GitHub repository. This is the primary path for engineering handoff: your team can review the code, open pull requests, and deploy from their existing workflow.
GitHub Sync works best as part of a repeatable cycle. Here is the pattern most teams follow:
1
Prototype in Chippy
Build and iterate on your app in the Chippy builder. Use preview to test, refine tools, and get the experience right.
2
Export at stable checkpoints
When the app reaches a stable state (a working feature, a completed flow, or a milestone), export to GitHub. This creates a snapshot your team can review.
3
Review with your team
Engineers, designers, and product managers review the exported code on GitHub using pull requests and code review. Feedback flows back to the builder for the next iteration.
4
Deploy from your production stack
Once the code is approved, deploy using your team’s existing CI/CD pipeline and infrastructure. Chippy stays in the prototyping and iteration loop; production deployment happens in your stack.