Skip to main content

How to visualize GitHub Actions workflow dependencies

Turn a repo’s GitHub Actions workflows into a graph of jobs and their needs: dependencies. Free, no sign-in, any public repository.

Why workflow YAML is hard to read

A GitHub Actions workflow describes jobs and the order they run in through needs: keys scattered across a YAML file. With more than a handful of jobs it becomes hard to see which jobs run in parallel, which ones block a deploy, and what a failing job holds up.

See every workflow as a graph

Paste a repository URL into RepoLens and open the Workflows tab. RepoLens reads the workflow files in .github/workflows and draws each one as a directed graph: one node per job, one edge per needs: dependency.

Jobs with no dependencies sit at the start and run in parallel; the chain of jobs leading to a deploy or release shows up as a path through the graph. Each job also shows its runner (runs-on) and how many steps it has.

What to look for

Long chains of jobs that depend on each other one at a time are the usual reason a pipeline is slow; jobs that don’t share outputs can often be split off to run in parallel.

A job that many others need is a single point of failure: if it is flaky, everything after it is too. And workflows with no edges at all are independent jobs, which is often exactly what you want for lint and test matrices.

Where CI fits in the rest of the repo

The Codebase Tour tab lists where the tests and CI configuration live and which commands the project uses to build and run, so you can go from the workflow graph to the scripts it calls.

Try it on a repository