Recipes
Each page below is one task: the screen you want, the keys that build it, and what to press once it is on screen.
Home shows what needs you, with no setup. These recipes cover the questions Home does not answer: a team's queue, one release branch, a group's CI, a second GitLab.
Clearing your review queue
Every merge request waiting on your review, oldest first, with the drafts left out.
Everything red in a group
Every pipeline that failed in a group and its subgroups today, with the failure reason on each row.
Release day
Three tabs for one release branch: ready to merge, still blocked, already merged.
Finding flaky pipelines
The pipelines you retried that failed again, and the failures that were never tests.
Two GitLab instances
A work instance and gitlab.com in one dashboard, with each token read from the environment.
Behind a corporate proxy
A private certificate authority, an egress proxy, an access-gateway header, and a read-only token.
Piping a view into a script
The rows of a pinned view as JSON, on standard output.
The three keys
Every recipe is the same three moves in the same order.
| Key | What it decides |
|---|---|
| b | Where to look. A group, a subgroup tree, a project, or nothing at all when the answer is instance-wide |
| f | What to keep. State, draft, labels, authors, approvals, dates |
| P | How to keep it. The result becomes a tab, and it is still there tomorrow |
Each recipe names the scope for b, the filter for f, and the tab name for P.
Filter values
Label names, usernames, branch names and project paths complete from your own instance as you type, so a recipe never depends on you spelling a value from memory. A value that does not exist cannot be submitted, and an empty result restates the query that produced it. See Filtering.