When your project outgrows Quick Start
What CI is, when your project needs it, and how to move from Quick Start to a GitHub repository you own.
What CI is
CI (continuous integration) is an automatic checklist that runs every time your code changes. It runs your tests and builds the project, so a change that breaks something that used to work is caught before it reaches anyone.
Your own checks and the Tester agent look at the change in front of them. CI re-checks everything, every time, including the parts nobody has touched in months.
When your project needs it
A simple website usually does not need CI. Your project is ready for it once it has any of these:
- A backend or an API
- Sign-in (authentication)
- Payments
- A database
These are the parts where a quiet break costs real users something, and where you want every change checked automatically.
Quick Start doesn't come with CI
Quick Start is built for simple projects and first experiments. The repository it creates doesn't come with CI.
When your project needs CI, move it to a GitHub repository you own and connect that repository to Operum. CI then runs on your own GitHub account, which is also where its cost is billed. Your agents can set CI up for you there; ask your PM.
Moving to your own repository
There is no one-click move. Operum gives you your project as a download, and the rest are steps you take yourself:
- Download your project. In Settings → Team, click Download zip, then Download handover file. The zip is your code; the handover file lists your open issues. Both links are valid for 1 hour, so download them straight away.
- Create a new, empty repository in your own GitHub account.
- Unzip the download and push the files into your new repository, for example with GitHub Desktop. The zip puts everything inside one top-level folder: push what is inside that folder. Include the hidden .operum folder, which holds your project knowledge.
- In Operum, create a new team and choose Connect Repo, pointing it at your new repository. Your Quick Start team stays a Quick Start team: there is no switch that converts it.
- Give the handover file to your PM in the new team and ask it to recreate your open issues. Nothing is recreated automatically.
What moves with you
- Your code, as it stands on the latest commit of the main (default) branch.
- Your project knowledge in .operum/knowledge/: goals, decisions and project context. It is stored in the repository, so it is in the zip.
- Your open issues, through the handover file: each one's title, description, labels and state.
What does not move
- Git history: commits, branches and tags. Your new repository starts with a single first commit.
- Work on other branches that was never merged into the main branch.
- Pull requests, review comments, issue comments and closed issues.
- Your team's activity log. It stays with the Quick Start team in Operum.
Two limits to know
- The download is capped at 100 MB. A larger project cannot be exported this way; contact support and we will get your code to you.
- Download links expire after 1 hour. If one expires, export again for fresh links.
How to confirm the move worked
Operum does not check the move for you. Before you stop using your Quick Start team, check these yourself:
- Your new repository on GitHub shows your files, including .operum/knowledge/.
- Your new team's agents are working in the new repository: ask your PM for a small change and see its pull request appear there.
- Your open issues are in the new repository's issue list.