Tour

MisteR Dashboard at work on the demo project, an invented online bookshop: the merge requests and what each one waits for, the diff and its review, comments and lead time.

From light to dark and back, through the open merge requests, the review's rhythm of three of them, a diff and its review notes, a merge request's comments, then the prompt that fixes what is red.

What each merge request waits for

Every open merge request on one line: its commits, comments and unresolved threads, its pipeline, Sonar issues, coverage and remaining mutants, how far it lags behind its target, and when it last moved.

The dashboard listing the open merge requests of the demo project, with their review, quality and lag columns.

The review's rhythm

Hover the commit count: the commits pile up over time, with the reviewers' comments and the author's answers on the curve. Whether fixes follow the comments shows at a glance.

The commit activity chart of a merge request, its cumulative commits with comments by others and by the author.

A diff that reads well

The commits grouped by push, the file list beside the code, renamed files, and the words that changed marked within each line.

The diff of a merge request side by side, with its pushes, its files and a renamed file.

Review notes in the diff

The threads sit on their lines, on either side, and the arrows go from one to the next. Reply, resolve or reopen without leaving the diff; quotes, code and lists show as in GitLab.

Review threads shown on their lines in the diff, one on a removed line, with Reply and Reopen buttons.

Large diffs too

Twenty-five files and ten thousand changed lines: each file is highlighted as it comes into view, and a very large one waits for a click.

A diff of twenty-five catalogue files, its file list scrolling on the left.

Comments

The merge request's comments as GitLab renders them, screenshots included, with a reply on each.

The comments page of a merge request: a mutation testing report, a long comment and one with a screenshot.

A prompt for your coding agent

The AI button writes the prompt that fixes what is red, from the failed pipeline, the surviving mutants and the unresolved threads, or runs your project's own actions, such as a review.

The AI dialog showing the fix prompt of a merge request with a failed pipeline and a surviving mutant.

The main branch

The latest pipeline of the main branch at the bottom, its stages and jobs, and its build times over the last builds.

The main branch pipeline expanded, with its build time chart and its stages.

Lead time

The merged ones, with the same review indicators and how long each took to develop, to stabilize and in total.

The merged view, listing merge requests with their total, development and stabilisation durations.

Light or dark

Every page comes in both themes; the browser remembers the choice.

The dashboard in the dark theme.

The diff in the dark

The same diff, in the dark theme.

The diff of a merge request in the dark theme.