There is now a video of the whole setup: Orbi Cloud: from zero to a tagged release in six steps. It runs 66 seconds, it is in English, and it has chapters, so you can jump to the step you are stuck on.
The six steps are the same six the status page counts:
- Sign in with your GitHub identity.
- Install the Orbi GitHub App on your account.
- Connect a repository — the repo and the base branch Orbi works from.
- Provision the environment. About a minute.
- Your first Issue. Label it
ai-ready, and Orbi writes the code and opens a pull request. - Cut a release. Type the version; Orbi bumps it, tags it and publishes the GitHub Release.
The sixth step is a decision, not a button
Steps one through five are setup: you are handing Orbi the things it cannot infer — an identity, an installation, a repository, a runtime. Step five is where it starts working on its own.
Step six is different, and the video says so out loud: you decide the version, Orbi never increments it for you. The runner will bump the version file, create the tag and publish the Release. It will not choose the number. A version is a claim about what changed and who should care — that is a product decision, and reading it off a counter would be pretending otherwise. The release scope comes from the Milestone carrying that exact title; without one, the release stops at scope derivation and tells you why.
That is also why the step exists at all in the onboarding bar. An engine that silently tagged releases would be easier to demo and worse to operate.
Step five is one label, and you can add it without leaving the terminal:
gh issue edit <number> --add-label ai-ready
What you are actually looking at
Every screen in the video is the product rendering, not a mockup: the sign-in card, the connect form with its repository and base-branch fields, the progress bar counting the step you are on, the connected-repository table with its provisioning status, the release form with the version box. The GitHub App page is the real one at github.com/apps/orbi-build.
If you want to read instead of watch, the same path is in the docs: docs.orbi.build. If you want to run the whole thing on your own machine instead of ours, that is the same product, open source and self-hostable.
Start here: orbi.build/cloud.