Skip to content

Commit 1681995

Browse files
committed
🐛 fix: pr feedback
1 parent 6eb6e3a commit 1681995

File tree

2 files changed

+4
-6
lines changed

2 files changed

+4
-6
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Azure DevOps was formerly known as Visual Studio Team Services (VSTS).
1313
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, all activities such as comments, work item creation, and commit associations 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.

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,16 +8,14 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo
88

99
<Alert>
1010

11+
<p>
1112
Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration.
12-
13-
</Alert>
14-
15-
<Alert title="Note">
13+
</p>
1614
<p>
1715
We recommend using a dedicated service account when installing this integration rather than a personal user account.
1816
</p>
1917
<p>
20-
Since the integration uses personal access tokens for authentication, all activities such as comments, work item creation, and commit associations 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.
2119
</p>
2220
<p>
2321
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.

0 commit comments

Comments
 (0)