Home
Home opens on launch and groups your work by what needs you next. It asks GitLab only about you, so it draws itself on a fresh install that knows nothing about your organisation.
Groups
The groups and their wording come from GitLab's own merge request homepage, which shipped in 17.9 and has been the default since 18.2. Home adds one block that page does not have: your failing pipelines.
Above the rule, everything is waiting on you. These groups count toward the attention badge:
Below the rule, everything is waiting on somebody else. Those four groups are collapsed by default and excluded from the count: waiting for approvals, waiting for assignee, approved by you, approved by others.
Rows carry GitLab's own substatus wording: Draft, Reviewers needed, Changes requested, Reviewer commented.
The four queries run concurrently behind one spinner, and a warm cache paints real rows before the first reply arrives. See refresh and caching.
The attention count
9 need you counts the groups above the rule and nothing else. Work that is waiting on somebody else stays out of the number, so the badge counts the things you can act on now.
What you can do
| Key | Action | Key | Action |
|---|---|---|---|
| j k | move | b | browse the rest of GitLab |
| Enter | focus the preview | f | filter this group |
| z Z | collapse a group, or all of them | P | pin what you are looking at |
| o | open in the browser | r | refresh |
Collapse state is remembered between runs. Reordering a built-in group, or hiding one, is two keys and is the whole customisation surface Home has.
The rest of your work
Home answers one question: what needs me. For a team's queue, a group's failed pipelines, or a release branch, press b and browse, narrow the result with the filter bar, then pin it so it is a tab tomorrow.