twin memory

GitLab

Your activity, to-dos, issues, merge requests and their threads on gitlab.com, in an end user's memory.

Your activity, to-dos, issues, merge requests and their threads on gitlab.com.

Connect it

In the console, open Connectors, pick GitLab, check whose memory it feeds, and Continue to GitLab. Sign in on gitlab.com and approve; you come back connected, and the last 90 days start arriving within a few minutes. See Overview for what happens to what it reads.

What it reads

SourceWhat it holdsRead
EventsYour pushes with their commit messages, branches you created or deleted, your comments, and the issues and merge requests you opened, merged or closedevery minute
IssuesIssues you created or are assigned to, and those still open at any age; deleted ones are reported endedevery minute
Merge requestsMerge requests you authored, are assigned to or review, with their merge status, and those still open at any age; deleted ones are reported endedevery minute
TodosYour to-dos - mentions, review requests, assignments, failed pipelines - and the ones you marked doneevery minute
DiscussionsComments, diff threads, approvals, assignments, review requests, state changes and label changes on the merge requests and issues that concern you; those on a deleted one are reported endedevery 2 minutes

On this page