Skip to main content

GitHub

The GitHub integration keeps a copy of your project's code in a GitHub repository. This page explains how to connect your account, link a repository, and keep the two in sync, and when a GitHub connection is worth setting up in the first place.

Why connect GitHub​

Your code always lives safely in Instroc, so GitHub is optional. It becomes useful when you want:

  • An off-platform backup of your code that updates as you build.
  • Code review using GitHub's pull request and diff tools.
  • Collaboration with developers who work in their own editors and want to read or discuss the code in a familiar place.

Even without GitHub, your full source code is always available as a ZIP download on every plan. See the Code editor page for how to view and download your code.

Connecting your account​

You will find GitHub in two places in the editor: the GitHub icon in the preview header (it reads "Connect to GitHub" before you connect, and "GitHub connected" after), and the GitHub section in the Workspace navigation. There is also a shortcut in the chat input's "+" menu.

Connecting uses your GitHub account directly. Click the connect button, approve access on GitHub, and you are linked. There are no keys to copy. The GitHub connection is available on every plan.

Creating or linking a repository​

Once your account is connected, the GitHub section gives you two paths:

  • Create a repository in one click. Instroc creates a new repo under your GitHub account and pushes your project's code to it.
  • Link an existing repository. Point the project at a repo you already have.

After that, you can push your code to the repository whenever you want a snapshot on GitHub, and you can import code from the repository into your project. You can unlink the repository at any time without affecting your project in Instroc.

Sync status​

The workspace GitHub section shows the current sync status and the last commit, so you can see at a glance whether GitHub has your latest changes. The preview header icon reflects your connection state while you work.

tip

Push after meaningful milestones, like finishing a feature or before a big restructuring. Combined with Instroc's own version history, that gives you two independent safety nets.

How it fits your workflow​

Most builders treat the repository as a mirror: Roc and the built-in code editor remain the place where the app is built, and GitHub holds the record. If a developer on your team wants to review a change, they read it on GitHub and leave comments there, then you make the change in Instroc and push again.

For sharing the app itself rather than the code, use workspace invites instead; see Plans for collaborator limits per tier. And remember that publishing your app has nothing to do with GitHub: you publish from the editor, and the live app updates when you press Update. See Publishing.