You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
+12-10Lines changed: 12 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,11 @@
1
1
---
2
2
title: GitLab
3
3
sidebar_order: 1
4
-
description: "Learn more about Sentry’s GitLab integration and how it helps you track and resolve bugs faster by using data from your GitLab commits."
4
+
description: "Learn more about Sentry's GitLab integration and how it helps you track and resolve bugs faster by using data from your GitLab commits."
5
5
---
6
6
7
+
<GitHubDomainChecker />
8
+
7
9
## Install
8
10
9
11
<Alert>
@@ -30,15 +32,15 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi
30
32
31
33

32
34
33
-
1. In the pop-up window, complete the instructions to create a Sentry app within GitLab. Once you’re finished, click "Next".
35
+
1. In the pop-up window, complete the instructions to create a Sentry app within GitLab. Once you're finished, click "Next".
34
36
35
37

36
38
37
39
1. Fill out the resulting GitLab Configuration form with the following information:
38
40
39
41
1. The GitLab URL is the base URL for your GitLab instance. If using gitlab.com, enter https://gitlab.com/.
40
42
41
-
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.
43
+
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.
42
44
43
45

44
46
@@ -52,13 +54,13 @@ Sentry owner, manager, or admin permissions and GitLab owner or maintainer permi
52
54
53
55
1. In the resulting panel, click "Authorize".
54
56
55
-
1. In Sentry, return to Organization Settings > **Integrations**. You’ll see a new instance of GitLab underneath the list of integrations.
57
+
1. In Sentry, return to Organization Settings > **Integrations**. You'll see a new instance of GitLab underneath the list of integrations.
56
58
57
-
1. Next to your GitLab Instance, click "Configure". _It’s important to configure to receive the full benefits of commit tracking._
59
+
1. Next to your GitLab Instance, click "Configure". _It's important to configure to receive the full benefits of commit tracking._
58
60
59
61

60
62
61
-
1. On the resulting page, click "Add Repository" to select which repositories in which you’d like to begin tracking commits.
63
+
1. On the resulting page, click "Add Repository" to select which repositories in which you'd like to begin tracking commits.
62
64
63
65

64
66
@@ -157,7 +159,7 @@ For certain native platforms, the stack trace will look different. In cases like
157
159
158
160

159
161
160
-
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`.
162
+
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`.
@@ -220,11 +222,11 @@ For more details, see the full documentation for [Code Owners](/product/issues/o
220
222
221
223
- Why am I getting a `500` response during installation or configuration?
222
224
223
-
- First, make sure you’ve allowed our IPs, which can be found [here](/security-legal-pii/security/ip-ranges/). The 500 response is coming from GitLab, so you may need to try again or double-check that your settings and permissions are correct in GitLab. You must have both owner/manager/admin permissions in Sentry as well as owner permissions in GitLab to successfully install this integration.
225
+
- First, make sure you've allowed our IPs, which can be found [here](/security-legal-pii/security/ip-ranges/). The 500 response is coming from GitLab, so you may need to try again or double-check that your settings and permissions are correct in GitLab. You must have both owner/manager/admin permissions in Sentry as well as owner permissions in GitLab to successfully install this integration.
224
226
225
227
- Why am I seeing an "Invalid Repository Names" error?
226
228
227
-
- GitLab takes into account the whitespace before and after the `/` . On the Repositories page (Organization Settings > Repositories), you’ll notice a space (for example, "Owner / Repo" as opposed to "Owner/Repo"), which will need to be included in any command you’re running. If you are using GitLab’s [environment variables](https://docs.gitlab.com/ee/ci/variables/#debug-tracing) to pass the repository as `CI_PROJECT_PATH` in a cURL request for example, it may not include the spaces and you’ll need to hardcode the name in order for it to work.
229
+
- GitLab takes into account the whitespace before and after the `/` . On the Repositories page (Organization Settings > Repositories), you'll notice a space (for example, "Owner / Repo" as opposed to "Owner/Repo"), which will need to be included in any command you're running. If you are using GitLab's [environment variables](https://docs.gitlab.com/ee/ci/variables/#debug-tracing) to pass the repository as `CI_PROJECT_PATH` in a cURL request for example, it may not include the spaces and you'll need to hardcode the name in order for it to work.
228
230
229
231
- Why am I always the reporter?
230
-
- When using the GitLab integration to create issues, the “reporter” field is populated as the person who set up the integration by default — this is not configurable.
232
+
- When using the GitLab integration to create issues, the "reporter" field is populated as the person who set up the integration by default — this is not configurable.
0 commit comments