GitLab
Connect GitLab.com to work with remote repos, run agent workflows, and bring commits, merge requests, issues, and review activity into recaps, planning, delivery, and insights.
GitLab is in private beta and enabled per workspace. The integration supports GitLab.com OAuth. Self-managed GitLab instances are not supported.
Connect GitLab
Each developer connects a GitLab.com account before agents or workflows need to read projects, commit changes, or open merge requests. This keeps commits, merge requests, comments, and project activity tied to the right person.
To connect, open GitLab integration settings and sign in on GitLab.com. After authorization, you return to the dashboard with the connection linked to the current workspace.
If the GitLab card still shows Coming Soon, your workspace does not have the beta enabled yet.
What GitLab adds
| GitLab activity | What it does |
|---|---|
| Commits | Help derive completed work and delivery context. |
| Merge requests | Appear in Merge & Pull Requests with other review work. |
| Push events | Keep commit activity current through GitLab webhooks. |
| Merge request events | Track review and merge state for delivery and measurement. |
| Comments and notes | Add review context where GitLab permissions allow it. |
| Issues | Can appear as synced work when GitLab issue activity is captured from connected projects. |
Open merge requests can appear in planned work. Merged merge requests can move into completed work. For capture behavior, see Captured Work.
Commit summaries
Commits from connected projects can be grouped into daily work summaries. If commit comments are enabled, the summary can also be posted back as a GitLab note.
Settings
Change these in GitLab settings.
| Setting | What it controls |
|---|---|
| Include personal repositories | Includes projects from your personal GitLab namespace. Off by default. |
| Disable commit comments | Prevents summaries from being posted back as GitLab commit notes. |
| Exclude groups | Stops activity from selected GitLab groups from feeding recaps, planning, and insights. |
| Exclude repositories | Stops selected GitLab projects from being tracked. |
GitLab does not use the GitHub contribution scanning setting. Personal projects come from your user namespace. Group projects follow GitLab group and project access.
Reconnects preserve excluded groups, excluded projects, personal repository settings, and commit comment preferences.
Where activity appears
GitLab activity appears in Recaps, Merge & Pull Requests, Insights, and Pull Request Flow. Link it to Initiatives when code should roll up to planned work, and track defects or incidents as Bugs.
Security and access
We never ask for your GitLab password. The integration uses GitLab.com OAuth and requests GitLab API access during connection.
GitLab OAuth tokens expire and refresh automatically when possible. If refresh fails or the grant is revoked, reconnect GitLab.
GitLab controls which groups and projects your account can access. We use GitLab metadata to build summaries and work context. We do not store your repository source code.
To disconnect completely, revoke the OAuth grant from your GitLab user settings or remove the integration from the workspace.