GitPipeline

Validation state: stages cannot be saved while errors remain. Warnings allow save but surface inline so the user knows the pipeline does not match the team's actual flow.

Error:
2 errors must be fixed before saving. A stage is missing a branch, and two stages map to the same status. Fix the highlighted rows below.
Warning:
1 warning. The order of branches does not match the team's GitHub branch protection. Review the pipeline preview at the bottom.

This board

monday2github Development

Board is set by the Monday view context.

Repository: Ideaplaces/monday2github-playground

1
When
, set status to
↓
2
When
, set status to
Warningmain is the production branch but is mapped to "Deployed to Dev." Likely reversed order.
↓
3
When
, set status to
↓
4
When
, set status to
ErrorStage has no branch. Pick a branch or remove this stage.
↓
5
When
, set status to
ErrorStatus "Deployed to Dev" is already used by stage 2. Each status can appear only once.

Pipeline preview (with issues)

PR opened

Code Review

→
main

Deployed to Dev

→
staging

Deployed to Staging

→
(no branch)

Deployed to Production

→
develop

Deployed to Dev

Status moves forward only. A push to an earlier stage's branch will not move a card backward.