Skip to main content
For Next.js TypeScript projects, Rocket supports full two-way sync with GitHub. Rocket pulls from your main branch and pushes changes to a rocket-update branch, automatically opening a pull request to main for each batch of code edits (manual changes, visual edits, and AI-generated). Pull changes made by teammates or in your local IDE back into Rocket.For all other frameworks, sync is one-way (push only).

​
How it works

DirectionWhat happensSupported projects
Push (Rocket → GitHub)Rocket pushes changes to the rocket-update branch and automatically opens a pull request to main for review.All frameworks
Pull (GitHub → Rocket)Imports the latest state of main back into your Rocket project, with conflict resolution if needed.Next.js TypeScript only

​
Push changes to GitHub

1

Click the GitHub icon

Click the GitHub icon in the toolbar.
2

Choose a repository

Select an existing repository or create a new one.
3

Push

Click Push to send your project code to GitHub. Rocket pushes to the rocket-update branch and automatically opens a pull request to main so your changes can be reviewed. Push again anytime to update with your latest changes.

​
Pull changes from GitHub

Available for Next.js TypeScript projects only. After your initial push, the GitHub button changes to Pull from GitHub.
1

Click Pull from GitHub

Click the Pull from GitHub button in the toolbar.
2

Resolve any conflicts

If changes in GitHub conflict with your Rocket project, Rocket surfaces them so you can choose how to resolve before the pull completes.
3

Continue building

Once the pull is complete, your preview updates automatically and you can keep iterating.
Rocket pulls from the main branch only. Changes on other branches will not be pulled into Rocket.

​
When to push vs pull

ScenarioAction
You iterated in Rocket and want to back up or sharePush to GitHub
A teammate committed changes in their IDEPull from GitHub into Rocket
You edited code locally and want to continue in RocketPull from GitHub into Rocket
You want to trigger a CI/CD pipelinePush to GitHub, then your pipeline runs

​
Disconnect from GitHub

GitHub is connected at the account level, not per task. Disconnecting removes the GitHub link for your entire Rocket account. To disconnect, open Connectors via the ... menu in the preview toolbar, or go to Workspace Settings → Connectors and click the GitHub card. See Manage connectors for full steps. Your task files in Rocket remain intact. To reconnect, go through the same steps and authorize a GitHub account.

​
Limitations

  • Next.js TypeScript only for pull. Two-way sync requires a Next.js project using TypeScript. JavaScript-only Next.js projects and all other frameworks support push only.
  • Branch behaviour. Rocket pulls from main and pushes to a rocket-update branch, opening a PR to main for each batch of changes. Other branches are not synced.
  • Manual sync. There is no automatic sync - push and pull manually when ready.
  • Paid feature. GitHub sync requires a paid Rocket plan.

​
One-way sync (other frameworks)

For non-Next.js or JavaScript-only projects, GitHub integration is push-only. Push your code to GitHub for backup and collaboration, but changes made directly in GitHub will not sync back to Rocket. Always make changes in Rocket first, then push.

See the full GitHub connector setup guide, including authorization and permissions.

​
What’s next?

From GitHub

Import an existing Next.js TypeScript repo to start building in Rocket.

Code tab

Browse and edit your project files directly in Rocket.

Netlify

Deploy your app to the web after pushing to GitHub.

GitHub connector

Connect your GitHub account, manage repository settings, and push code.