Skip to main content
Connect GitHub and push your task code to a repository with one click. Rocket handles the Git setup automatically, no terminal needed. For most frameworks, GitHub integration is one-way: Rocket pushes code to a rocket-update branch and opens a pull request to main. For Next.js TypeScript tasks, two-way sync is supported. After the initial push, the button changes to Pull from GitHub so you can bring changes from main back into your task.

​
What you can do

Automated backups

Push your Rocket project to GitHub whenever you want a snapshot of your work. Click the GitHub icon in the toolbar and push.

Team collaboration

Share your codebase with teammates by pushing to a shared GitHub repo. They can review, fork, or clone your code from there.

CI/CD pipelines

Once your code is on GitHub, connect it to services like GitHub Actions, Vercel, or Netlify for automated builds and deployments.

Open-source portfolio

Publish your Rocket projects as public repositories to build a developer portfolio or contribute to open source.

​
Connect GitHub

GitHub connects via OAuth, so no API key is needed. It is a workspace-level connector, so connect it once and it is available across all tasks.
You can connect from four places. All do the same thing.Option 1: When creating a task (Clone from GitHub)Click the + button at the lower left of the input box on the home screen and select Clone from GitHub. If you have not connected GitHub yet, Rocket prompts you to authorize at this point.

Import from GitHub

Clone a Next.js TypeScript repo and continue building with AI.
Option 2: From the GitHub button in the toolbarClick the GitHub icon in the top-right of the code view toolbar. A popup opens with a Connect button.
GitHub connect popup showing a Connect button.GitHub connect popup showing a Connect button.
Option 3: From the Connectors tabClick the ... button in the preview toolbar, then select Connectors.
Toolbar dropdown with Connectors option highlighted.Toolbar dropdown with Connectors option highlighted.
Click the GitHub card, then click Connect.
Connectors panel showing the GitHub card with a Connect button.Connectors panel showing the GitHub card with a Connect button.
Option 4: From workspace Settings

Connect from workspace Settings

Connect once from Settings and it is available across all tasks.
After clicking ConnectYou are redirected to GitHub’s authorization page. Sign in if prompted, review the permissions, and click Authorize DhiWisePvtLtd.
GitHub OAuth authorization page for rocket.new.GitHub OAuth authorization page for rocket.new.
After authorization you are redirected back to Rocket with GitHub connected.
Permissions Rocket requests from GitHub: create new repositories on your behalf, read public and private repo names and metadata, and access your GitHub username and email address.
Disconnect

Disconnect a service

Disconnect or switch accounts from workspace Settings.

​
Push to GitHub

  1. Click the GitHub icon in the toolbar.
  2. Choose an existing repository or create a new one.
  3. Click Push to send your task code to GitHub.
GitHub push dialog showing repository selection and Push button.GitHub push dialog showing repository selection and Push button.
Push again anytime to update the repository with your latest changes. Rocket pushes to the rocket-update branch and opens a pull request to main each time. For Next.js TypeScript tasks, the button changes to Pull from GitHub after the initial push. Use it to bring in the latest state of main from your local IDE or from teammates and continue building in Rocket.

​
Tips

  • Two-way sync for Next.js TypeScript. After pushing, the button switches to Pull from GitHub so you can import changes from main back into Rocket.
  • One-way sync for other frameworks. Non-Next.js tasks support push only. Always make changes in Rocket first, then push.
  • Branch behaviour. Rocket pushes to rocket-update and opens a PR to main. Pull always reads from main.
  • Repository naming. Rocket can create new repos or push to existing ones. Use a clear name so tasks are easy to find.
  • Public vs. private. Public repos are great for portfolios. Private repos are better for client work or proprietary tasks.
  • Manual sync. There is no automatic sync. Push manually when you are ready.
  • Permissions are scoped. Rocket only requests access to create repos and read metadata. It does not delete repos or modify existing code on GitHub.

​
What’s next?

Code sync

Two-way sync for Next.js TypeScript projects. Push changes out and pull external edits back in.

Netlify

Deploy your Rocket app to the web. Works great after pushing code to GitHub.

Code tab

Learn more about browsing and managing your project’s source code in Rocket.