Each stage in a pipeline targets a branch. When a run reaches the stage, DIJJI.ai opens a pull request against that branch. This page covers changing the branch an existing stage points at — for example, repointing a Staging stage from staging to release. To add a new stage, see Add a stage to a pipeline; for what stages do, see The pipeline: stages and gates.
Open the stage
From your project, select Pipeline. The stages appear as a row in the Pipeline Flow card. Select the stage you want to change — its Stage Configuration panel opens below the row.
Edit the Branch field
In the panel, find the Branch field. It’s a required field, marked with an asterisk, and you type the branch name in free-form (e.g. main, dev, staging).
Clear the current value and type the new branch name. A branch name can be up to 256 characters. DIJJI.ai doesn’t create the branch for you — type the name of a branch that already exists in the repository, or one your team will create before the next run reaches this stage.
The “no repository connected” warning
If the project has no GitHub repository connected, the Pipeline page shows an amber notice:
No GitHub repository connected. Branch validation is unavailable. Connect a repository in project settings to verify branch existence.
You can still type and save a branch name — but DIJJI.ai can’t check that the branch exists until a repository is connected. To connect one, see Connect GitHub.
Save
Changing the branch isn’t applied until you save. While you have unsaved edits, the page shows “Unsaved changes. Click Save to apply.” and a Discard button appears next to Save — select Discard to drop the change and restore the stage’s last saved branch.
Select Save. A Save Pipeline dialog confirms how many stages you’re saving. Select Save Pipeline to confirm. If the Branch field is empty, DIJJI.ai marks the problem instead of saving — fill it in and save again. When the save succeeds, the page shows “Pipeline saved.”
The new branch applies to runs that start after you save.
Stage branch vs. trunk branch
The Branch field on a stage is not the same as the Trunk Branch setting lower on the Pipeline page. The trunk branch is where DIJJI.ai creates feature branches from; a stage’s branch is where that stage’s pull request is opened against. They’re often different — and on a multi-stage pipeline, each stage has its own branch. Changing one doesn’t change the other.