Every pipeline stage has a gate — the condition that decides whether a run may move on to the next stage. There’s no single “gate type” menu: the gate is shaped by three settings in the stage’s Stage Configuration panel on the project’s Pipeline page. For how to set them, see Choose a gate type for a stage; for what gates are, see The pipeline: stages and gates.
Every stage opens a pull request, and that pull request must be merged before the run advances. The settings below decide who merges it and what else must be true first.
The gate settings
| Setting | Values | What it does |
|---|---|---|
| Auto-merge PR | Off (default) / On | Off: the run waits in the Waiting for Gate state until you merge the stage’s pull request — merging is the approval. On: DIJJI.ai merges the pull request itself and the run flows straight through, with no pause. |
| Wait for deploy confirmation | Off / On | On: after the pull request is merged, the stage holds until the merged code is confirmed deployed, so the run doesn’t move ahead of the deployment. See Deploy confirmation and the deploy wait. |
| E2E trigger | None / Automatic / Manual | When set to Automatic or Manual, the stage also waits for end-to-end tests before it clears. See Trigger E2E tests manually. |
The main control is Auto-merge PR: leaving it off is a human checkpoint (the run stops for your merge), turning it on is hands-off. Most pipelines mix the two — Auto-merge off on the stages that need a careful look, on where a pause would only slow you down. A common shape is a human merge on every stage except a hands-off final one. Turning Auto-merge on for a production stage skips human review, and the merge can fail if the branch has protection rules.
End-of-stage behavior
Separate from the gate, each stage has an end-of-stage behavior — what happens once the stage is fully done:
| Behavior | Effect |
|---|---|
| Advance to the next stage | The run moves on to the next stage. This is the default. |
| Stop — pipeline ends here | The pipeline ends at this stage. Valid only for the final stage. |
The gate decides when a stage is done; the end-of-stage behavior decides what happens next. An intermediate stage must advance — setting it to stop would strand the stages after it.
How the conditions combine
When more than one is in play, a stage clears its gate in this order:
- Pull request merged — by you (Auto-merge off) or by DIJJI.ai (Auto-merge on). Always required.
- Deploy confirmed — only if Wait for deploy confirmation is on.
- E2E tests passed — only if the E2E trigger is set to Automatic or Manual.
Once all the conditions that apply have cleared, the stage is done and its end-of-stage behavior decides what happens next.