Skip to main content
Version: 0.1.145

Staging

Staging is one shared branch per project, called repave-staging unless you name it otherwise, where you merge features and modules — finished or not — so you can run them together before any of them is delivered.

The problem it solves​

Features and modules are built one at a time, each on its own branch, each checked on its own. That tells you each works alone. It does not tell you they work together, and the interactions between two pieces of work — the same screen, a schema change another one relies on — are where the interesting failures live. The earlier you see them, the cheaper they are: staging lets you put half-built work side by side, long before delivery.

Stage a feature or module​

Open the feature's or the module's page and click Stage. Its branch, as it is now, is merged into the staging branch; the button becomes Staging… while that runs, then Staged.

  • On a feature that belongs to a module, the button reads Stage module: the feature's work lives on its module's branch, so the whole module is staged.
  • When the branch has moved on since you staged it, the button reads Update staging, and the Staging page marks the item New commits. Click either to stage its new commits.
  • The button is not shown when there is nothing to stage: the branch has nothing the base lacks, the work is already delivered, or you can only view the project.

Staging never changes the feature or module branch. Everything a stage does — including any fix to a conflict — happens on the staging branch only.

When staged work conflicts​

If a branch you stage conflicts with what is already on staging, an agent resolves the conflict on the staging branch. Its fix is accepted only when the merge is complete, no conflict markers are left, and the project's build check passes; the tests are not run, because staged work may be unfinished and is expected to fail some of them.

If the agent cannot get there in its attempts, staging is left exactly as it was and the Staging page says so, with Retry and a link to the agent's run.

The Staging page​

Staging in the sidebar lists everything on the branch, who staged it and when, and whether each item has new commits or has since been delivered. Opening it starts the staging environment, and the app runs in the inline browser, the same way a feature's or module's preview does. Newly staged work appears in a running environment without a restart.

While a step runs, the page shows what it is doing — merging, resolving conflicts, checking the build, pushing. Steps you ask for while one is running wait their turn and run in order.

Update from the base​

Staging does not follow your integration branch on its own. Click Update from main (named after your project's base branch) to merge the latest base into staging; a conflict is resolved the same way as when staging a branch.

Reset staging​

Reset staging, in the page's ⋯ menu, removes everything staged and puts the staging branch back to the base branch. Conflict fixes made on staging are lost; feature and module branches are not changed. You are asked to confirm.

The branch in your repository​

The staging branch is pushed to your project's repository after every step, so your own CI or deployment can pick it up. On a project that combines several repositories, it is pushed to the combined repository only.

The branch belongs to Repave. If someone pushes to it outside Repave, staging stops and the Staging page says the branch has commits Repave didn't make; Reset staging discards them and staging carries on. A reset is the only time Repave force-pushes the branch.

If you name the staging branch after one your repository already has — your team's own staging, say — Repave leaves that branch alone: staging stops before touching it, and the Staging page asks you to choose another name in Project Settings. The same happens when the name is the branch your work is delivered to.

Naming the staging branch​

Change the name under Project Settings → Integrations → Staging branch, then Save Changes.

  • Before anything is staged, the new name is simply used from the first stage on.
  • Once staging holds work, the branch is renamed in place: what is staged stays staged, the new name is pushed to your repository, and the old one is deleted there. The field reads Renaming to … until that is done, and the Staging page shows it like any other step.
  • If the rename can't finish — for example, your repository refuses to delete the old name — the Staging page says what is left, and Retry finishes it.

A name is refused when it isn't a valid branch name, when it is the branch your work is delivered to, when it starts with feature/ or module/ (Repave's own branches), or when a branch of that name already exists in your repository. Git keeps branch names as folders, so a name also can't sit beside an existing branch that way: repave/staging is refused while a repave branch exists.

Staging is never delivered. Features and modules are still delivered one at a time, as before.