What Syncs
Once connected, your project and its repository stay aligned:- Fabricate to GitHub — code the agent generates is committed to your repository.
- GitHub to Fabricate — commits you or your collaborators push to the repository flow back into your project.
GitHub Sync uses webhooks to detect changes on the repository side, so updates pushed to GitHub are picked up automatically.
Setting Up GitHub Sync
1
Open GitHub Sync for your app
In your Fabricate project, find the GitHub Sync option in the code management settings.
2
Authorize Fabricate with GitHub
Connect your GitHub account so Fabricate can access the repository you want to sync with.
3
Choose a repository
Select the GitHub repository to link to this app.
4
Confirm the connection
Fabricate sets up two-way sync, including the webhook that watches for changes pushed to the repository.
5
Build and push as usual
Keep prompting in Fabricate or commit directly on GitHub — changes stay in sync both ways.
Sync vs. a One-Time Export
GitHub Sync is an ongoing connection. Exporting your code is a one-time snapshot.
Choose GitHub Sync when you want to keep working across both Fabricate and GitHub. Choose a one-time export when you just want a copy of your code as it stands.
Frequently Asked Questions
Do I need an existing repository?
Do I need an existing repository?
GitHub Sync connects your app to a GitHub repository. If you only want a fresh copy of your code in a brand-new repo, you can push to a new repository instead.
Who owns the code in the repository?
Who owns the code in the repository?
You do. The repository is yours — Fabricate syncs to it, but there’s no lock-in. See Exporting Your Code.
Can I edit code locally and have it show up in Fabricate?
Can I edit code locally and have it show up in Fabricate?
Yes. That’s the point of two-way sync — push commits to the connected repository and they flow back into your Fabricate project.
Where to Go Next
Export Code
Push to a new repo or download a zip.
File Explorer
Browse the code that gets synced.