← Teams

Dependency graph

See which repos depend on each other, and trigger downstream pipelines when an upstream changes.

What it shows

The dependency graph is a visual map of which repos in your org depend on each other. Nodes are repos, edges are declared dependencies. It answers "if I change this repo, what else might break?"

Declaring dependencies

Add a depends section to your repo's .gittan.yaml:

# .gittan.yaml
depends:
  - repo: shared-types
    cascade: true

When cascade: true, a successful pipeline in the upstream repo triggers a pipeline run in the downstream repo. This is how you propagate library changes through your dependency chain without manual intervention.

Where to find it

The dependency graph is in the org admin panel under Dependencies. It renders all repos and their connections. Hover a node to highlight its direct dependencies and dependents.

Why this matters

In a polyrepo setup, understanding cross-repo dependencies is critical. The graph makes implicit relationships explicit, and cascade pipelines make sure changes propagate correctly.