GitPipeline

Connect repositories to this board and define how each branch maps to a status. Status moves forward only.

Board settings

This board

monday2github Development

GitPipeline is installed as a view on this board. The board is set by Monday — no need to pick.

All repositories below write to this column.

Info:
GitPipeline is a forward-only pipeline, not isolated automations. Stages are ordered: earlier stages are upstream, later stages are downstream. Once a card reaches a downstream stage, an event for an upstream stage will not move it backward.

Connected repositories

2 repos

Repository 1

Drag to reorder. Stage 1 is the entry, last stage is downstream.
☰1
When
, set status to
↓
☰2
When
, set status to
↓
☰3
When
, set status to
↓
☰4
When
, set status to

Pipeline preview

PR opened

Code Review

→
develop

Deployed to Dev

→
staging

Deployed to Staging

→
main

Deployed to Production

Repository 2

Drag to reorder. Stage 1 is the entry, last stage is downstream.
☰1
When
, set status to
↓
☰2
When
, set status to
↓
☰3
When
, set status to

Pipeline preview

PR opened

Code Review

→
develop

Deployed to Dev

→
main

Deployed to Production

Other events (do not change status)

These webhooks log task activity and post comments but never move the status. They are not stage transitions. Toggle them per org. Defaults shown.

Pull request opened

Post a "PR #N opened by {author}" comment on the linked Monday task.

Pull request merged

Post a "PR #N merged into {branch}" comment. The status change is handled by the pipeline stage that matches the target branch.

Pull request closed without merge new

Post a "PR #N closed without merge by {author}" comment so the assignee sees the signal. No status change.

Commits on a feature branch new

Roll commits pushed to a non-pipeline branch (e.g. fix/foo) into a single accumulating comment on the linked task. Updates the same comment on each push instead of creating new ones.

Stage deploys (pipeline branches)

Post a "Deployed to {stage}" comment when a commit lands on a pipeline branch. This is in addition to the status change.