When a run reaches a stage’s gate, it stops and waits — it can’t advance until the gate’s condition is met. This page covers getting that run moving again. For what a gate is and why a stage has one, see The pipeline: stages and gates.
Check what the gate is waiting for
A run held at a gate sits in the Waiting for Gate state. Open the run detail page for the run — the status badge near the top doesn’t just tell you the run is stopped, it names the action that clears it. For the most common gate, it reads Merge PR.
Only a stage that waits for a human merge stops a run this way — one with its Auto-merge PR setting off. A stage with Auto-merge PR turned on merges its own pull request, so the run flows straight through and never lands in Waiting for Gate.
Open the stage and its pull request
Each stage the run has reached appears as a card on the run detail page. Expand the card for the stopped stage. Inside it you’ll see:
- A Pull Request link — the pull request DIJJI.ai opened against the stage’s branch. That pull request is the delivery for the stage.
- A Waiting for PR merge notice, confirming the run is paused on you until the pull request is merged.
Follow the Pull Request link — it opens the pull request on GitHub.
Review, then merge
The gate is your checkpoint on the result of a stage. Review the pull request the way you’d review a teammate’s: read the diff, confirm it does what the task asked, and let whatever checks your repository runs on a pull request finish.
When you’re satisfied, merge the pull request on GitHub. Merging is how you clear the gate — nothing advances the run until the merge happens.
If the pull request isn’t right, don’t merge it. Leave the run where it is while you decide; to end the attempt instead, cancel the run.
The run continues on its own
Once GitHub confirms the merge, DIJJI.ai picks it up — you don’t press anything. Back on the run detail page you’ll see:
- The stage’s pull request gains a Merged badge.
- The run leaves Waiting for Gate, returns to Running, and moves on to the next stage.
DIJJI.ai learns about the merge from GitHub, so there’s a short delay between merging and the page catching up. Give it a moment and refresh if the page still shows the old state.
Force the run past the gate
Merging is the normal way to clear the gate. If you need to move the run on without satisfying the gate, a Force Next Stage button appears at the top of the run detail page while a stage is held. Selecting it opens a confirmation — Force next stage? — that warns it will bypass the current stage’s gate and advance to the next stage. Choose Force next stage to do it.
Use this deliberately: forcing past a merge gate advances the run even though the pull request hasn’t been merged. If the stage is instead waiting on its E2E tests, the stage card offers a Skip E2E button (see Trigger E2E tests manually); if it’s waiting on deploy confirmation, a Force Advance button appears once enough time has passed since the merge (see Deploy confirmation and the deploy wait).
Merging a pull request is a GitHub action, available to anyone with write access to the repository. Force Next Stage isn’t admin-only either — any member of the project’s team can use it.
For every state a run can pass through, and the other ways a run pauses for you, see Run states.