Skip to content

Commit 010e6a2

Browse files
armenzgmrduncan
andauthored
chore(derived_code_mappings): Remove call out (#14283)
It's always been a source of confusion since it would not make any mention of the automatic code mapping derivation (only available for GitHub). There are also some automatic commit fixes. --------- Co-authored-by: Matt Duncan <14761+mrduncan@users.noreply.github.com>
1 parent cc4f7cc commit 010e6a2

File tree

4 files changed

+8
-26
lines changed

4 files changed

+8
-26
lines changed

docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,10 +10,10 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS).
1010

1111
<Alert title="Note">
1212
<p>
13-
We recommend using a dedicated service account when installing this integration rather than a personal user account.
13+
We recommend using a dedicated service account when installing this integration rather than a personal user account.
1414
</p>
1515
<p>
16-
Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration.
16+
Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration.
1717
</p>
1818
<p>
1919
Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization.
@@ -104,12 +104,6 @@ When Sentry sees this, we’ll automatically annotate the matching issue with re
104104

105105
### Stack Trace Linking
106106

107-
<Alert>
108-
109-
This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
110-
111-
</Alert>
112-
113107
Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).
114108

115109
1. Navigate to **Settings > Integrations > Azure DevOps > Configurations**.

docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -174,12 +174,6 @@ When Sentry sees this, we’ll automatically annotate the matching issue with re
174174

175175
### Stack Trace Linking
176176

177-
<Alert>
178-
179-
This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
180-
181-
</Alert>
182-
183177
Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).
184178

185179
1. Navigate to **Settings > Integrations > Bitbucket > Configurations**.

docs/organization/integrations/source-code-mgmt/github/index.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ There are two types of GitHub integrations, so make sure you're choosing the cor
1212
- `https://ghe.example.com/`
1313

1414
For these accounts, follow the '[Installing GitHub Enterprise](#installing-github-enterprise)' instructions.
15-
15+
1616

1717
### Check Your Domain
1818

@@ -67,9 +67,9 @@ The following permissions are required for the GitHub integration to work correc
6767
| <span>Members<br/><em>_[Org-level]_</em></span> | Read-only | To map organization users to GitHub identities for improved issue attribution and collaboration. |
6868
| Metadata | Read-only | To identify repository structure, names, default branches, and visibility. |
6969
| Pull Requests | Read & Write | To write comments on pull requests for (1) issues caused by the pull request and (2) to highlight existing issues in the code diff.|
70-
| Webhooks | Read & Write | To subscribe to real-time updates like push events, PRs, and issues.
70+
| Webhooks | Read & Write | To subscribe to real-time updates like push events, PRs, and issues.
7171

72-
Occasionally, Sentry will request additional permissions to your GitHub account as new features are introduced. Denying or ignoring the request to update will not affect your current Sentry usage, but may prevent access to future features.
72+
Occasionally, Sentry will request additional permissions to your GitHub account as new features are introduced. Denying or ignoring the request to update will not affect your current Sentry usage, but may prevent access to future features.
7373

7474
## Installing GitHub Enterprise
7575

@@ -328,7 +328,7 @@ By default, this feature is automatically enabled once your GitHub integration h
328328

329329
<Alert>
330330

331-
Sentry will automatically try to set up code mappings on C#, Go, JavaScript, Node.js, PHP, Python, and Ruby projects for organizations with the GitHub integration installed. If your project uses a different SDK, you can add code mappings manually. Support for other languages and other source code integrations is being worked on.
331+
Sentry will automatically try to set up code mappings on C#, Clojure, Go, Groovy, Java, JavaScript, PHP, Python, Ruby, and Scala for organizations with the GitHub integration installed. If your project uses a different SDK, you can add code mappings manually.
332332

333333
</Alert>
334334

docs/organization/integrations/source-code-mgmt/gitlab/index.mdx

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -12,10 +12,10 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo
1212
Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration.
1313
</p>
1414
<p>
15-
We recommend using a dedicated service account when installing this integration rather than a personal user account.
15+
We recommend using a dedicated service account when installing this integration rather than a personal user account.
1616
</p>
1717
<p>
18-
Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration.
18+
Since the integration uses personal access tokens for authentication, activities such as comments and work item creation will be attributed to the user who installed the integration.
1919
</p>
2020
<p>
2121
Using a service account helps maintain proper access control, prevents disruption when team members leave, and ensures consistent attribution for all features across your organization.
@@ -118,12 +118,6 @@ A `<SHORT-ID>` may look something like 'BACKEND-C' in the image below.
118118

119119
### Stack Trace Linking
120120

121-
<Alert>
122-
123-
This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
124-
125-
</Alert>
126-
127121
Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default **branch**).
128122

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

0 commit comments

Comments
 (0)