RoRo Quantum
Open console
Reference · Chapter 10 of 14

Sharing & GitHub

Snapshot links out, read-only imports in.

~2 min read3 sectionssame text as the guide inside the lab
All chapters
Overview
Start here
Getting started
Working in the lab
Projects & files Run a circuit Python in the browser Notebooks Circuit builder & emulator Library Copilot
Reference
Machines & credits Sharing & GitHub Keyboard shortcuts
Playbooks
For hackathons For teams & integration For researchers

Keys are written for macOS, the way the lab prints them — on Windows and Linux read ⌘ as Ctrl, ⌥ as Alt, ⇧ as Shift, ↵ as Enter.Keys are shown for Windows / Linux to match your platform — on a Mac, Ctrl is ⌘ and Alt is ⌥. Every binding: Keyboard shortcuts.

On this page
Share a projectImport from GitHubGetting work out

Two doors: a read-only snapshot link out, and a read-only import in from GitHub. Neither one can change your files behind your back.

Share a project

Share in the title bar (or ⌘⇧P → Share this project…) takes a snapshot server-side and gives you a link like lab.roroquantum.com/s/<token>. Copy it, Preview it in a new tab, or Revoke link later. The dialog states the terms:

  • Anyone with the link can read the files. No sign-in needed.
  • It is a snapshot: what you share now stays what they see, however much you edit after.
  • Read-only. It carries nothing about your account or credits.
  • Whoever opens it can run the circuit themselves — on their own credits, after signing in. The share page offers Copy into my lab (or Sign in and run it), which forks the snapshot into a project of theirs.

Revoking turns the page into a "this share was revoked" notice. Deleting a file later does not touch a snapshot already shared.

Import from GitHub

The Source control rail (the branch icon) imports; it deliberately does not push — the lab is where you experiment, your repository stays the thing you control.

  1. Paste github.com/owner/repo, owner/repo, or a gist URL, and press Load.
  2. Read the plan: which files would arrive and which are skipped, each with a reason (binary, too large, over the 80-file cap…). Nothing is created yet.
  3. Press Import as a new project. Files are fetched one by one with a progress count; the new project opens.

If the deployment has GitHub OAuth configured, a Connect GitHub button appears; after connecting, a My repos tab lets you browse your own repositories (private included), pick a branch and a sub-folder, and import through the server proxy. The token never enters this app — the popup's only message back is "connected". Disconnect forgets it.

Getting work out

Integrate rail → Export: Project .zip (every text file), Submission bundle (files + a generated README manifest + runs.csv — what a hackathon judge wants), Run history CSV. Per run, the Runs rail's ⋯ menu exports the manifest, counts and a standalone histogram. Import .zip on the same panel brings a project back in. Runs and their results stay in your account regardless of the project.

Related: Projects & files · For teams & integration