BuildMonitor as it draws today, staged and photographed headlessly by the UI test harness. The owners, repositories and runs are invented and the clock is stopped, so nothing here comes from a real CI service. The pictures are regenerated on every successful build of main, so they show the current interface.
Every workflow the providers found, across GitHub owners and Azure DevOps projects, one row per build and branch with the most recently started first. Running builds show their progress against an estimate taken from recent successful runs, with an ETA; the history column shows the last five finished runs, and each row counts down to its next poll, sooner for builds that are running or have just failed.
Each GitHub owner and each Azure DevOps organization has a tab of its own. Icons beside a repository's name mark it as private or a fork, and a repository with no workflows is still listed.
A failed run's errors are read from its job logs. Clicking them opens the whole list.
Right-clicking a row opens links to the repository, the workflow, the branch and the latest run, and on GitHub can re-run, cancel or trigger the workflow.
What the monitor has been doing, colour-coded by level: discovery, run transitions, rate-limit pacing and anything that failed.
