How it works
From the workspace, open Push to GitHub and provide:- Repository —
owner/name. It can be an existing repo or one the export creates for you, private or public. - Branch — where to push.
- A GitHub personal access token with permission to push (a fine-grained token works; GitHub’s token settings page is linked from the dialog).
Your token is never stored
The access token lives in the dialog for the current session only — it is never persisted anywhere, not even in your browser’s storage. The convenience details (repo name, branch, visibility, when you last pushed) are remembered per project so repeat pushes are quick; the token is asked for each session, on purpose.What’s in the export
Your app’s source, as it exists in the workspace — pages, components, API routes, configuration, migrations. Build artifacts and dependency caches (node_modules, build output) and Creator’s internal bookkeeping are excluded,
the same way a well-kept repository would exclude them. Clone it, run
npm install, and it’s a normal project.
When to use it
- Handoff — transferring ownership of a finished app to a client is a push to their repository. See Clients & handoff.
- Backup and portability — keep your own copy on your own terms, at any point in the build.
- Working outside Creator — the exported project is standard code; your team can take it from there whenever you choose.