inline

Platform dashboard

Headline figures compared with the window before them, every open issue from every module in one list, the pull request flow timed stage by stage, and spend against your budget. A developer sees their own pull requests and never spend.

1:30 · narrated, with captions · Security and the platformRead about Platform

Chapters

What it covers

  • Needs attention
  • Pull request flow
  • Spend by module
  • Permissions

The inline dashboard in 90 seconds: headline figures against the previous window, one list of open issues, review activity, PR flow and spend.

Read about Platform

Transcript

The narration as spoken, by chapter. Select a time to play the film from there.

Intro

The inline dashboard: everything inline does, on one page.

Headline figures

The headline figures compare each number with the window of the same length just before it.

Needs attention

Needs attention puts every open issue, from every module, in one list, worst first. There's nothing to refresh. As work lands, the page updates itself.

Review activity

Review activity charts every day, by volume, kept rate, latency or spend.

Finding outcomes

Finding outcomes show what your team did with each finding, once its pull request closed.

Pull request flow

The pull request flow times each stage up to merge, at the median, P75 or P90.

Repositories and spend

The repository table puts every module's signal on one row. Spend splits cost by module, against your budget.

Filters and export

Filters live in the address, so a link shares the exact view. And Export downloads the table.

Permissions

And everyone sees it narrowed to what they may read: a developer gets their own pull requests, and never spend.

GitHub

When inline needs more from GitHub, it updates your webhooks itself, and asks an owner only for what they must approve. inline. See the whole platform, and act on what matters.

Put it on one repository

Connect GitHub or GitLab, enable a repo, and the next pull request opened gets a review.