What each GitLab card shows

You have added a GitLab card. Here is what it lists, and for which projects.

Which projects a card reads

A card reads the GitLab projects of the components of your catalog that name their project with the gitlab.com/project-slug annotation, with your own token. A component without the annotation is not read. See Show the GitLab tab on a component for the annotation.

metadata:
  annotations:
    gitlab.com/project-slug: acme/shop-api   # <namespace>/<project> on GitLab

Each row ends with an arrow: click it to open the pipeline, job, merge request or release in GitLab.

Pipelines

The last pipeline of each branch, when it failed or ran lately.

Column	What it shows
Resource	The project, with a coloured dot for the status of the pipeline
Title	The branch
Author	The GitLab username of the person who triggered it
Date	When it ran, most recent first

The statuses present in the card are written at the top right of the card, with their colour: for example running, success.

Detailed Pipelines

The jobs of your latest pipelines. One row per job.

Column	What it shows
Resource	The project
Title	The name of the job
Date	When it ran
Duration	How long it took, for example 27s
Status	running, success, …
Stages	The status of the job's stage, as a coloured mark

Merge Requests

The merge requests of every GitLab project of the catalog that your token can read, whoever opened them: the open ones, and those closed in the last 7 days.

Column	What it shows
Resource	The project, with a coloured dot for the state of the merge request
Title	The title of the merge request
Author	The GitLab username of its author
My role	What you are on it: Author, Review requested, Assignee or None
Date	Its last update

The states present are written at the top right of the card, for example open.

To keep only yours, filter the column My role and save the filter with the card: remove None in the Filters tab of the card, as for the GitHub Pull Requests card, see Change or remove a card. If GitLab holds too many merge requests to read them all, the card says List cut: too many items to read, only the most recent are shown. above the table.

A card with merge requests in it was not checked on a live instance (no GitLab connected); it works like the GitHub Pull Requests card.

Releases

The last published release of each GitLab project of your catalog that your token can read.

Column	What it shows
Resource	The project
Key	The tag of the release, for example v1.2.0
Date	The date of the release

To-Do List

Your pending GitLab to-dos: reviews requested, assignments, mentions, broken builds. When you have none, the card says No pending to-do on GitLab. A card with to-dos in it was not checked on a live instance.

When there is nothing to show

A card with no row says Nothing here yet and, under it, what would fill it. Click Learn more under the sentence to come back to this page.

Card	What it says
Merge Requests	No open merge request in the GitLab projects named by the components of the catalog (gitlab.com/project-slug annotation) that your token can read.
Pipelines and Detailed Pipelines	No pipeline failed or ran lately in the GitLab projects that your token reads and that a component of the catalog names (gitlab.com/project-slug annotation).
Releases	No release published in the GitLab projects named by the components of the catalog (gitlab.com/project-slug annotation) that your token can read.
To-Do List	No pending to-do on GitLab, then: GitLab lists no pending to-do for your account: no review requested, assignment, mention or broken build.

Change what a card shows

1. On My Dashboards, open the tab of the dashboard.

2. At the top right of the card, click the more button, then Edit. The Edit card window has three tabs:

   Tab	What you do
   General	Rename the card or change its icon
   Columns	Switch a column off
   Filters	Remove a value from a column, so its rows disappear

3. Click Save.

The same menu has Refresh, to read GitLab again now, and Delete.

✅ That's it!

Next: Get GitLab notifications.