DIJJI.ai Academy

How-to guides

Add a stage to a pipeline

A stage is one step on the path your work travels. This page covers adding one to a pipeline that already exists. If your project has no pipeline yet, start with Design your first pipeline instead — it walks through building one from scratch. For what stages and gates mean, see The pipeline: stages and gates.

Open the Pipeline page

From your project, open Deliver, then select Pipeline. The existing stages appear as a row, laid out left to right with arrows between them.

Add the stage

You have two ways to add a stage:

  • Select Add Stage at the top right of the Pipeline Flow card.
  • Select the dashed + button at the end of the stage row.

Either one does the same thing. DIJJI.ai appends a new stage to the end of the row, selects it, and opens its Stage Configuration panel below.

The new stage starts with placeholder settings — a name like Stage 3, an empty branch, and a gate of None. It isn’t usable until you fill it in.

A pipeline can hold up to 20 stages. At the limit, both Add Stage controls are disabled.

Configure the new stage

In the Stage Configuration panel, set the three fields that matter:

  • Stage name (required) — what you call this step, for example Staging. Up to 100 characters. Each name must be unique within the pipeline.
  • Branch (required) — the branch this stage targets, typed in free-form (e.g. main, dev, staging). When a run reaches the stage, DIJJI.ai opens a pull request against this branch.
  • Auto-merge PR — the stage’s gate. Every stage opens a pull request that must be merged before the run advances; this setting decides who merges it. Off (the default) pauses the run until you merge the stage’s pull request — the human checkpoint. On lets DIJJI.ai merge it for you so the run flows straight through. Leave it off on a stage you want to review.

The panel has more settings beyond those three:

  • Wait for deploy confirmation — on by default for a stage you add. While it’s on, the run pauses after the stage’s pull request is merged until a deployment is confirmed. Turn it off for a stage with nothing to deploy. See Deploy confirmation and the deploy wait.
  • Free the project while this stage waits — off by default. When on, the project is released while this stage waits (for a merge, deploy, or E2E tests) so queued tasks can run; this run resumes automatically when the project is free.
  • End-of-stage behavior — advance to the next stage by default; set it to stop only on the final stage of the pipeline.
  • E2E trigger and its testing fields — None, Automatic, or Manual. When the trigger is anything other than None, an E2E Targets list appears: select + Add target to add each deployed part you want tested. Each target takes a Title (for example Web App, Backoffice, or API), a check type — Browser or API — a URL, and an optional throwaway Test Username / Test Password login. Add as many targets as the stage needs. Leave the trigger on its default to put a working stage in place; see Trigger E2E tests manually when you want a stage to run tests.

The default that catches people out is Wait for deploy confirmation: a freshly added stage has it switched on, so a run will hold at that stage after its pull request is merged. If you don’t have a deployment wired up, turn it off.

Quality and reasoning depth aren’t set per stage. They live on the Engine Configuration card under the project’s Settings, where you pick a quality-versus-speed tier and a reasoning-depth tier (a deeper tier costs more). That choice applies to the whole project, so you don’t need to touch it when adding a stage. See Engine Configuration for the full list of options.

Position the stage

A new stage always lands at the end of the row. To move it earlier — for example, to slot a Staging stage between Development and Production — drag the stage card by its handle into the new position. Stages run in the order shown, left to right.

Save

Adding a stage isn’t applied until you save. While you have unsaved edits, the page shows “Unsaved changes. Click Save to apply.”

Select Save. A Save Pipeline dialog confirms how many stages you’re saving. Select Save Pipeline to confirm.

If the new stage is missing its name or branch, or its name duplicates another, DIJJI.ai marks the problem instead of saving. Fix it and save again. When the save succeeds, the page shows “Pipeline saved.”