Skip to content

feat(Gitlab): Updated gitlab integration and seer docs #18383

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Dhrumil-Sentry merged 4 commits into from
Jun 12, 2026
Merged

feat(Gitlab): Updated gitlab integration and seer docs #18383

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
75df860
Updated gitlab integration and seer docs to include seer features for…
Jun 11, 2026
a67b9cf
Adding note that it's in beta.
Jun 11, 2026
70c6108
Making sure other files referencing Seer integrations include Gitlab.
Jun 11, 2026
1586bc2
defining MR to be merge request
Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/integrations/source-code-mgmt/github/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ description: >-
og_image: /og-images/organization-integrations-source-code-mgmt-github.png
---

The GitHub integration connects your repositories to Sentry to bring [commit tracking](#commit-tracking), [suspect commits](#suspect-commits-and-suggested-assignees), [stack trace linking](#stack-trace-linking), [issue management](#issue-management), and [PR comments](#get-sentry-comments-on-pull-requests), into the contexts that Sentry uses to help debug issues and power [Seer AI features](#configure-github-integration) like Autofix and Code Review. It also supports [resolving issues via commit or PR](#resolve-via-commit-or-pull-request) and [Code Owners](#code-owners) for automatic issue routing.

There are three types of GitHub integrations, so make sure you're choosing the correct one:
- [GitHub](#installing-github) - For individual GitHub users/organizations (as well as most GitHub Enterprise Cloud customers), so long as they are hosted on `github.com`. Follow the '[Installing GitHub](#installing-github)' instructions, **Please begin the installation from Sentry**.

Expand Down
58 changes: 41 additions & 17 deletions docs/integrations/source-code-mgmt/gitlab/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,8 @@ description: >-
og_image: /og-images/organization-integrations-source-code-mgmt-gitlab.png
---

The GitLab integration connects your repositories to Sentry to bring [commit tracking](#commit-tracking), [suspect commits](#suspect-commits), [stack trace linking](#stack-trace-linking), and [issue management](#issue-management) into the contexts that help Sentry debug issues and power [Seer AI features](#seer) like Autofix and Code Review. It also supports [resolving issues via commit or merge request (MR)](#resolve-via-commit-or-pull-request) and [Code Owners](#code-owners) for automatic issue routing.

## Install

<p>
Expand All @@ -30,39 +32,39 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi

1. Navigate to **Settings > Integrations > GitLab**.

![Install GitLab integration](./img/gitlab-overview.png)
![Install GitLab integration =600x](./img/gitlab-overview.png)

1. In the resulting modal, click "Add Installation".

![Connect Sentry to a GitLab instance](./img/add-installation.png)
![Connect Sentry to a GitLab instance =600x](./img/add-installation.png)

1. In the pop-up window, complete the instructions to create a Sentry app within GitLab. Once you’re finished, click "Next".

![Configuration modal and Sentry app within GitLab](./img/configuration-modal.png)
![Configuration modal and Sentry app within GitLab =600x](./img/configuration-modal.png)

1. Fill out the resulting GitLab Configuration form with the following information:

1. The GitLab URL is the base URL for your GitLab instance. If using gitlab.com, enter https://gitlab.com/.

2. Find the GitLab Group Path in your group’s GitLab page. Groups might contain subgroups and projects. You should not specify the URL to any specific project, just to a group or subgroup.

![GitLab page showing group path](./img/gitlab-groups.png)
![GitLab page showing group path =600x](./img/gitlab-groups.png)

3. Find the GitLab Application ID and Secret in the Sentry app within GitLab.

![GitLab application id and secret](./img/gitlab-app-id.png)
![GitLab application id and secret =600x](./img/gitlab-app-id.png)

4. Use this information to fill out the GitLab Configuration and click "Submit".

![GitLab configuration form](./img/gitlab-configuration.png)
![GitLab configuration form =600x](./img/gitlab-configuration.png)

1. In the resulting panel, click "Authorize".

1. In Sentry, return to Organization Settings > **Integrations**. You’ll see a new instance of GitLab underneath the list of integrations.

1. Next to your GitLab Instance, click "Configure". _It’s important to configure to receive the full benefits of commit tracking._

![GitLab instance with connected group and highlighted configure button](./img/configure-button.png)
![GitLab instance with connected group and highlighted configure button =600x](./img/configure-button.png)

1. On the resulting page, click "Add Repository" to select which repositories in which you’d like to begin tracking commits.

Expand All @@ -78,37 +80,37 @@ Issue tracking allows you to create GitLab issues from within Sentry and link Se

1. Select your issue

![List of unresolved issues](./img/sentry-unresolved-issues.png)
![List of unresolved issues =600x](./img/sentry-unresolved-issues.png)

1. Navigate to Linked Issues on the right panel of the issue's page and click "Link GitLab Issue".

![GitLab logo with Link GitLab Issue text](./img/link-gitlab-issue.png)
![GitLab logo with Link GitLab Issue text =600x](./img/link-gitlab-issue.png)

1. You have two options to complete the issue link:

1. In the pop-up, you can fill out the appropriate details in the _Create_ tab, and then click "Create Issue".

![pop-up modal to create issue](./img/gitlab-create-issue.png)
![pop-up modal to create issue =600x](./img/gitlab-create-issue.png)

1. Or, in the pop-up, you can click the Link tab, search the issue by name, and then click "Link Issue". _Issues aren't currently searchable by number._

![pop-up modal to search issue name](./img/link-issue-by-name.png)
![pop-up modal to search issue name =600x](./img/link-issue-by-name.png)

1. To unlink an issue, click on the "X" next to its name under Linked Issues.

![GitLab logo and project next to an X icon](./img/unlink-issue.png)
![GitLab logo and project next to an X icon =600x](./img/unlink-issue.png)

### Commit Tracking

Commit tracking allows you to hone in on problematic commits. With commit tracking, you can better isolate what might be problematic by leveraging information from releases like tags and metadata.

Once you've configured both [release and commit tracking](/product/releases/), you'll be able to see more thorough information about a release: who made commits, which issues were newly introduced by this release, and which deploys were impacted.

![Dashboard with last commit highlighted](./img/last-commit-in-releases.png)
![Dashboard with last commit highlighted =600x](./img/last-commit-in-releases.png)

When you investigate deeper into that commit, you can leverage information from metadata like tags.

![Issue detail highlighting tags](./img/highlighting-tags.png)
![Issue detail highlighting tags =600x](./img/highlighting-tags.png)

Broadly, this lets you isolate problems in order to see which commits might be problematic.

Expand All @@ -120,7 +122,7 @@ Once you've added a repository (see configuration step 8), you can start resolvi

A `<SHORT-ID>` may look something like 'BACKEND-C' in the image below.

![Issue detail highlighting suspect commits](./img/short-id.png)
![Issue detail highlighting suspect commits =600x](./img/short-id.png)

### Stack Trace Linking

Expand Down Expand Up @@ -155,7 +157,7 @@ First, navigate to a stack trace that you wish to map. Find an **In App** frame,

For certain native platforms, the stack trace will look different. In cases like these, you can find the absolute path by hovering over the filename.

![Highlighting where in the UI to find the file path for native stack traces](./img/code-mappings-stacktrace-native.png)
![Highlighting where in the UI to find the file path for native stack traces =600x](./img/code-mappings-stacktrace-native.png)

If you aren’t sure, you can look at the event JSON by clicking on the `{}` button in the event header. Find the text in the frame's `filename` or `abs_path`.

Expand All @@ -181,7 +183,7 @@ Once you've set up stack trace linking, Sentry can use information from your sou

After pinpointing the suspect commit, you can also identify the developer who made the commit and assign them the task of fixing the error.

![Issue detail highlighting suspect commits](./img/highlighting-suspect-commits.png)
![Issue detail highlighting suspect commits =600x](./img/highlighting-suspect-commits.png)

Learn about setting up this functionality in [Suspect Commits](/product/issues/suspect-commits/).

Expand All @@ -193,8 +195,30 @@ Import your existing GitLab CODEOWNERS files to automatically assign Sentry issu

For more details, see the full documentation for [Code Owners](/product/issues/ownership-rules/#code-owners).

## Seer

<Alert>
The Gitlab Seer integration is currently in early beta, slowly opening up to more organizations. Please reach out to support@sentry.io if you are interested in trying it out.
</Alert>

With the GitLab integration connected, you can use Seer's AI features, including [Autofix](/product/ai-in-sentry/seer/autofix/) and [Code Review](/product/ai-in-sentry/seer/code-review) with your GitLab repositories.
Comment thread
sentry[bot] marked this conversation as resolved.

**Autofix** analyzes Sentry issues using your GitLab repo code as context and can open a merge request with the proposed fix directly in GitLab.

**Code Review** reviews your merge requests for potential errors. Trigger it by commenting `@sentry review` on any MR. Automatic reviews also run when a merge request is opened or updated.

<Alert>
GitLab does not support the GitHub Checks API. Code Review results appear as MR comments, not as a pipeline status check. You cannot use Seer as a required GitLab CI/CD check.
</Alert>

To set up Seer with GitLab, go to [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) and connect your GitLab repositories. Only GitLab.com (cloud) is supported.

## Troubleshooting

- Does Seer support GitLab?

- Yes. Autofix and Code Review both work with GitLab.com repositories. Self-hosted GitLab is not currently supported for Seer features.

- I'm using GitLab on-premises. Do I need to allow Sentry's IP addresses?

- Yes. You can find our IP ranges [ here ](/security-legal-pii/security/ip-ranges/).
Expand Down
2 changes: 1 addition & 1 deletion docs/product/ai-in-sentry/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Use Seer to:

- **[Fix Issues](/product/ai-in-sentry/seer/autofix/)**: Use Autofix to find root causes and generate suggested code fixes for errors and performance issues, or hand off to a [coding agent](/product/ai-in-sentry/seer/autofix/#handoff-to-claude-code-or-cursor-cloud-agents).
- **[Investigate Problems](/product/ai-in-sentry/seer/#seer-agent)**: Ask Seer Agent questions about your application and Seer Agent will do the digging. Walk through complex production problems with Seer Agent reasoning through evidence in real time.
- **[Review Code Changes](/product/ai-in-sentry/seer/code-review/)**: Have Seer review your code changes in GitHub, catching bugs before merging pull requests.
- **[Review Code Changes](/product/ai-in-sentry/seer/code-review/)**: Have Seer review your code changes in GitHub or GitLab, catching bugs before merging.

### Issue Summary

Expand Down
10 changes: 6 additions & 4 deletions docs/product/ai-in-sentry/seer/autofix/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,13 @@ keywords:
- github
---

**Autofix** is a collaborative workflow to find the root cause of, and solution to, issues. It uses Sentry's context (issue details, tracing data, logs, and profiles), your codebases (integrated through GitHub), and its interactions with you to identify and reason through problems in your code. Autofix can propose a solution, or be configured to follow through and open a PR with the solution.
**Autofix** is a collaborative workflow to find the root cause of, and solution to, issues. It uses Sentry's context (issue details, tracing data, logs, and profiles), your codebases (integrated through GitHub or GitLab), and its interactions with you to identify and reason through problems in your code. Autofix can propose a solution, or be configured to follow through and open a PR with the solution.

## Getting Started

Set up Issue Autofix in your organization or on specific projects:

1. Connect to GitHub through the [Sentry GitHub integration](/integrations/source-code-mgmt/github/). You can follow the steps in [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) to get started. **Note:** Seer can only be integrated with the cloud version of GitHub.
1. Connect to GitHub through the [Sentry GitHub integration](/integrations/source-code-mgmt/github/) or Gitlab through the [Sentry GitLab integration](/integrations/source-code-mgmt/gitlab/). You can follow the steps in [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) to get started. **Note:** Seer supports GitLab.com and GitHub.com (cloud versions only).

@billyvg billyvg Jun 12, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We support GHE too


2. Select which repositories you want to connect to Sentry, go to [Seer SCM Settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/scm/) to make sure your repositories are connected.

Expand Down Expand Up @@ -110,6 +110,8 @@ snippets and examples, and does not affect workflows involving your own coding a

Seer always performs root cause analysis and solution planning using its own internal tools and Sentry context. At the final code generation step, instead of having Seer generate the code fix directly, you can hand off to an external coding agent for implementation. Seer passes along the root cause and solution plan so the coding agent can act on them. This lets you leverage the strengths of specialized code generation tools while still benefiting from Seer's debugging and analysis.

When your codebase is connected via GitLab, Seer will open a merge request instead of a pull request. Coding agent handoff (Claude Code, Cursor) works the same way regardless of SCM provider.

@billyvg billyvg Jun 12, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems like kind of a random spot to mention it. I think it's better somewhere higher up where we first reference a PR or Pull Request. And just clarify that we use the term Pull Request everywhere in app but it is equivalent to Merge Request in Gitlab terminology


Supported coding agents for handoff:

- **Claude Code** — Seer passes the root cause and solution as a structured prompt that Claude Code can act on directly in your terminal or CI environment.
Expand Down Expand Up @@ -142,7 +144,7 @@ Seer handles access to a wide variety of data sources and tools. While debugging
- **Issue details**: Error messages, stack traces, and event metadata from your [Issues](/product/issues/)
- **Tracing data**: Distributed [traces](/concepts/key-terms/tracing/#whats-a-trace) and span information
- **Logs**: Structured [Logs](/product/explore/logs/) from your application (beta)
- **Your codebases**: Relevant code from linked GitHub repositories, with support for multiple repos for distributed services
- **Your codebases**: Relevant code from linked GitHub or GitLab repositories, with support for multiple repos for distributed services
- **Performance data**: Profiles and performance metrics
- **Interactive feedback**: Your input and guidance during the process
- **Sentry Docs**: Sentry's documentation site
Expand All @@ -167,5 +169,5 @@ Seer already automatically parses rules files from [Cursor](https://docs.cursor.
- For JavaScript / TypeScript projects that are minified in production, upload [source maps](/platforms/javascript/sourcemaps/) to Sentry for the best results.

<Alert level="info">
Currently, the cloud version of GitHub is the only SCM supported by Seer.
Seer supports GitHub.com and GitLab.com (cloud versions only). Self-hosted instances and other SCM providers (Bitbucket, Azure DevOps) are not currently supported.
</Alert>
Loading
Loading