From 75df860f6c350ec912bac9e5f37536d829282800 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Thu, 11 Jun 2026 13:30:53 -0700 Subject: [PATCH 1/4] Updated gitlab integration and seer docs to include seer features for gitlab. --- .../source-code-mgmt/github/index.mdx | 2 + .../source-code-mgmt/gitlab/index.mdx | 54 +++++++++++++------ .../ai-in-sentry/seer/autofix/index.mdx | 10 ++-- docs/product/ai-in-sentry/seer/index.mdx | 10 ++-- 4 files changed, 50 insertions(+), 26 deletions(-) diff --git a/docs/integrations/source-code-mgmt/github/index.mdx b/docs/integrations/source-code-mgmt/github/index.mdx index 4bccc52a60a23a..904fc0a94121bb 100644 --- a/docs/integrations/source-code-mgmt/github/index.mdx +++ b/docs/integrations/source-code-mgmt/github/index.mdx @@ -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**. diff --git a/docs/integrations/source-code-mgmt/gitlab/index.mdx b/docs/integrations/source-code-mgmt/gitlab/index.mdx index 478e2775d607db..6fd5cd66af17fb 100644 --- a/docs/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/integrations/source-code-mgmt/gitlab/index.mdx @@ -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 MR](#resolve-via-commit-or-pull-request) and [Code Owners](#code-owners) for automatic issue routing. + ## Install

@@ -30,15 +32,15 @@ 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: @@ -46,15 +48,15 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi 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". @@ -62,7 +64,7 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi 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. @@ -78,25 +80,25 @@ 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 @@ -104,11 +106,11 @@ Commit tracking allows you to hone in on problematic commits. With commit tracki 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. @@ -120,7 +122,7 @@ Once you've added a repository (see configuration step 8), you can start resolvi A `` 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 @@ -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`. @@ -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/). @@ -193,8 +195,26 @@ 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 + +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. + +**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. + + +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. + + +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/). diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index a1bc99e906364d..479254e914f6d9 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -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). 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. @@ -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. + 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. @@ -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 @@ -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. -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. diff --git a/docs/product/ai-in-sentry/seer/index.mdx b/docs/product/ai-in-sentry/seer/index.mdx index e0518ea6759168..1c1fd42c347def 100644 --- a/docs/product/ai-in-sentry/seer/index.mdx +++ b/docs/product/ai-in-sentry/seer/index.mdx @@ -20,7 +20,7 @@ Seer provides end-to-end debugging tools to help you troubleshoot and fix errors - **PR Creation**: Use Autofix to generate a code fix and create a PR. - **External Coding Agents**: Delegate Seer's analysis to an external coding agent for debugging and fixes. - [**Seer Agent**](#seer-agent): Ask any question about your application and Seer Agent finds the right telemetry to answer it. -- [**Code Review**](#code-review): Have Seer review your code changes in GitHub, catching bugs before merging pull requests. +- [**Code Review**](#code-review): Have Seer review your code changes in GitHub or GitLab, catching bugs before merging. @@ -28,7 +28,7 @@ Seer provides end-to-end debugging tools to help you troubleshoot and fix errors To start using Seer's capabilities follow these steps: -1. Connect to GitHub through the [Sentry GitHub integration](/integrations/source-code-mgmt/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/). **Note:** Seer supports GitHub.com and GitLab.com (cloud versions only). 2. Turn on Seer features for your projects and repos - [Enable Issue Autofix, delegate to Coding Agents](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/), and enable [Code Review](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/repos/). @@ -53,7 +53,7 @@ Once Autofix has run, Seer will provide remediation recommendations. **PR Creation** -You can prompt Seer to generate PRs to fix your issue, and push it to GitHub. You can add more context in natural language, or any external supporting information, to help Seer generate a better PR. **Note:** You must install the [Seer GitHub app](/integrations/source-code-mgmt/github/#installing-the-seer-github-app) to use this feature. +You can prompt Seer to generate PRs, or merge requests on GitLab, to fix your issue and push the changes to your repository. You can add more context in natural language, or any external supporting information, to help Seer generate a better fix. Note: You must install the Seer Github or GitLab app to use this feature. **External Coding Agents** @@ -91,7 +91,7 @@ You can also use Seer Agent in Slack as a part of the [Slack integration](/integ ### Code Review -[AI Code Review](/product/ai-in-sentry/seer/code-review/) helps you reviews your code changes, predicting errors and offering suggestions for improvement before merging pull requests. This feature is only available on GitHub. +[AI Code Review](/product/ai-in-sentry/seer/code-review/) reviews your code changes, predicting errors and offering suggestions for improvement before merging pull requests or merge requests. Code Review is available on GitHub and GitLab.com. ## What Seer Uses @@ -100,7 +100,7 @@ Seer is a powerful debugging agent, with access to a wide variety of data source - **Issue Context**: 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 Codebase**: Relevant code from linked GitHub repositories, with support for multiple repos for distributed services +- **Your Codebase**: 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 From a67b9cfc9aab9771bea113cd66b869eb261a8640 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Thu, 11 Jun 2026 13:34:51 -0700 Subject: [PATCH 2/4] Adding note that it's in beta. --- docs/integrations/source-code-mgmt/gitlab/index.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/integrations/source-code-mgmt/gitlab/index.mdx b/docs/integrations/source-code-mgmt/gitlab/index.mdx index 6fd5cd66af17fb..18b368733de54b 100644 --- a/docs/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/integrations/source-code-mgmt/gitlab/index.mdx @@ -197,6 +197,10 @@ For more details, see the full documentation for [Code Owners](/product/issues/o ## Seer + +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. + + 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. **Autofix** analyzes Sentry issues using your GitLab repo code as context and can open a merge request with the proposed fix directly in GitLab. From 70c6108e0e2832f714db5b6525d5567369488077 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Thu, 11 Jun 2026 13:53:08 -0700 Subject: [PATCH 3/4] Making sure other files referencing Seer integrations include Gitlab. --- docs/product/ai-in-sentry/index.mdx | 2 +- .../ai-in-sentry/seer/code-review/index.mdx | 26 +++++++++++++------ 2 files changed, 19 insertions(+), 9 deletions(-) diff --git a/docs/product/ai-in-sentry/index.mdx b/docs/product/ai-in-sentry/index.mdx index 9c2b73225c082c..d9bfcffba48a0c 100644 --- a/docs/product/ai-in-sentry/index.mdx +++ b/docs/product/ai-in-sentry/index.mdx @@ -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 diff --git a/docs/product/ai-in-sentry/seer/code-review/index.mdx b/docs/product/ai-in-sentry/seer/code-review/index.mdx index de27ef2a04dfce..1f3005bfbc6784 100644 --- a/docs/product/ai-in-sentry/seer/code-review/index.mdx +++ b/docs/product/ai-in-sentry/seer/code-review/index.mdx @@ -10,19 +10,21 @@ keywords: - code review - ai code review - pull request + - merge request - github + - gitlab - error prediction --- -**Code Review** helps you reviews your code changes, predicting errors and offering suggestions for improvement before merging pull requests. +**Code Review** helps you review your code changes, predicting errors and offering suggestions for improvement before merging pull requests or merge requests. ![Code Review =700x](./img/code-review-comment.png) ## Getting Started -Set up Code Review in your GitHub organization or on specific repositories: +Set up Code Review in your Github or GitLab organization or on specific repositories: -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 GitHub.com and GitLab.com (cloud versions only). 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. @@ -31,7 +33,7 @@ Set up Code Review in your GitHub organization or on specific repositories: **Note:** Enabling Code Review for one a repository starts *active contributor pricing*. Learn more about [Seer pricing](/pricing/#seer-pricing). -Currently Seer only supports the [GitHub integration](/integrations/source-code-mgmt/github/). +Seer supports the [GitHub integration](/integrations/source-code-mgmt/github/) and the [GitLab integration](/integrations/source-code-mgmt/gitlab/) (GitLab.com only). Self-hosted instances and other SCM providers are not currently supported. ### GitHub Permissions @@ -49,13 +51,17 @@ If you've already installed the GitHub integration, you may need to update your Denying or ignoring permission update requests won't affect your current Sentry usage, but will prevent Code Review and other features from working. +### GitLab Permissions + +For GitLab, Code Review uses the permissions granted during the [GitLab integration setup](/integrations/source-code-mgmt/gitlab/#install). The service account used for installation needs at least Maintainer access to the repositories you want Code Review to run on. + ## Code Review Commands Ways Code Review can help you: -1. **Error Prediction** - When you create a pull request and set it to `Ready for Review`, Code Review will check for errors in your code on every commit. Once the check is complete, you will see a 🎉 emoji as a reaction to your PR description. If errors are found, Code Review will add comments to your PR. **Note:** We skip reviews if you set your PR to `draft` at any time. +1. **Error Prediction** - When you create a pull request on Github, or a merge request on GitLab and set it to `Ready for Review`, Code Review will check for errors in your code on every commit. Once the check is complete, you will see a 🎉 emoji as a reaction to your PR/MR description. If errors are found, Code Review will add comments. **Note:** We skip reviews if you set your PR/MR to `draft` at any time. -2. **`@sentry review`** - Use this command in a PR comment, and the assistant will review the PR and predict errors, as well as make suggestions. Head to [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) to enable it. +2. **`@sentry review`** - Use this command in a PR or MR comment, and the assistant will review the changes and predict errors, as well as make suggestions. Head to [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) to enable it. ## GitHub Status Checks @@ -82,15 +88,19 @@ The detailed code review comments are also visible to all users with repository While you can add Code Review as a part of your branch protection, we recommend making the Code Review status check an **optional** check. Requiring it will block PR merges if the check fails due to service disruptions, and may conflict with future personal configuration options that allow users to opt out of code review. +### GitLab: No Status Checks + +GitLab does not have an equivalent to the GitHub Checks API. On GitLab, Code Review results appear as MR comments only — not as a pipeline status check. You cannot use Code Review as a required check in GitLab CI/CD merge request approvals. + ## Frequently Asked Questions - **What data does AI Code Review need access to for the AI system to function, and what information is sent to third-party AI providers?** AI Code Review requires access to your pull requests, including PR metadata, repository information, file names, directory structures, and code diffs. Only file names, code diffs, and PR descriptions are sent to the AI provider for analysis. -- **Does AI Code run anywhere outside of GitHub, and does it run in the background?** +- **Which SCM providers does Code Review support?** - AI Code Review only runs on GitHub. It will run when a PR is marked `ready for review` (either when creating the PR, or after taking it out of draft), on every commit while in `ready for review` mode, and when triggered by a comment. + Code Review runs on GitHub.com and GitLab.com (cloud versions only). Self-hosted instances and other SCM providers are not currently supported. On GitHub, it runs when a PR is marked `ready for review`, on every commit while in that mode, and when triggered by a comment. On GitLab, it runs when a merge request is opened or updated, and when triggered by commenting `@sentry review` on the MR. You can learn more about AI privacy and security [here](/product/ai-in-sentry/ai-privacy-and-security/). From 1586bc29c6cc27bff95c19257cbbec7599adca66 Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Thu, 11 Jun 2026 14:56:24 -0700 Subject: [PATCH 4/4] defining MR to be merge request --- docs/integrations/source-code-mgmt/gitlab/index.mdx | 2 +- docs/product/ai-in-sentry/seer/code-review/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/integrations/source-code-mgmt/gitlab/index.mdx b/docs/integrations/source-code-mgmt/gitlab/index.mdx index 18b368733de54b..e34c386446b8fd 100644 --- a/docs/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/integrations/source-code-mgmt/gitlab/index.mdx @@ -7,7 +7,7 @@ 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 MR](#resolve-via-commit-or-pull-request) and [Code Owners](#code-owners) for automatic issue routing. +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 diff --git a/docs/product/ai-in-sentry/seer/code-review/index.mdx b/docs/product/ai-in-sentry/seer/code-review/index.mdx index 1f3005bfbc6784..9bd36a6ac5e6cf 100644 --- a/docs/product/ai-in-sentry/seer/code-review/index.mdx +++ b/docs/product/ai-in-sentry/seer/code-review/index.mdx @@ -59,7 +59,7 @@ For GitLab, Code Review uses the permissions granted during the [GitLab integrat Ways Code Review can help you: -1. **Error Prediction** - When you create a pull request on Github, or a merge request on GitLab and set it to `Ready for Review`, Code Review will check for errors in your code on every commit. Once the check is complete, you will see a 🎉 emoji as a reaction to your PR/MR description. If errors are found, Code Review will add comments. **Note:** We skip reviews if you set your PR/MR to `draft` at any time. +1. **Error Prediction** - When you create a pull request on Github, or a merge request on GitLab and set it to `Ready for Review`, Code Review will check for errors in your code on every commit. Once the check is complete, you will see a 🎉 emoji as a reaction to your PR or merge request (MR) description. If errors are found, Code Review will add comments. **Note:** We skip reviews if you set your PR/MR to `draft` at any time. 2. **`@sentry review`** - Use this command in a PR or MR comment, and the assistant will review the changes and predict errors, as well as make suggestions. Head to [Seer settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/seer/) to enable it.