Skip to main content
Connect GitHub to Rocket 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 use it for

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.

​
Quick start

1

Click the GitHub icon

Click the GitHub icon in the toolbar.
2

Connect your account

In the popup, click Connect. You will be redirected to GitHub’s authorization page. Sign in, review permissions, and click Authorize DhiWisePvtLtd.
3

Choose a repository and push

Select an existing repository or create a new one, then click Push to send your task code to GitHub.

​
Detailed setup

​
Connect GitHub to Rocket

GitHub integration is managed through the Code tab. There are no chat commands for GitHub actions.
You can connect GitHub from two places:From the toolbar (fastest)
  • Click the GitHub icon in the toolbar.
  • In the popup, click Connect to begin authorization.
Connect to GitHub dialog with a Connect button.Connect to GitHub dialog with a Connect button.
You will be redirected to GitHub’s authorization page. Sign in if prompted, review the permissions, then click Authorize DhiWisePvtLtd.
GitHub OAuth authorization page for rocket.new showing repository, personal data, and workflow permissions.GitHub OAuth authorization page for rocket.new showing repository, personal data, and workflow permissions.
From ConnectorsIn the preview toolbar, click the ... button and select Connectors. Click the GitHub card and then click Connect.From workspace SettingsClick your workspace name in the top-left corner, select Settings, then click Connectors in the left sidebar. Click the GitHub card and then click Connect.

Workspace connectors

This connector is managed at the workspace level. Connect it once and it is available to all tasks.
After authorization, you will be 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.
  • Access your GitHub username and email address.
Update or disconnectOpen Connectors (via ... or workspace Settings → Connectors). Click the GitHub card and click Disconnect. To switch accounts, disconnect and reconnect with a different account. See Manage connectors for full steps.

​
How to push code

  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.
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 and limitations

  • 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.

​
Advanced guides

Code sync

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

​
What’s next?

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.