From a297b92b72230b6281d46d9d46b9d7326ea15191 Mon Sep 17 00:00:00 2001 From: Zayne Zhang Date: Thu, 29 Oct 2026 20:49:17 +0000 Subject: [PATCH] docs: shorten GitLab token scope explanations Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> --- platform/repositories/gitlab.mdx | 15 ++++----------- 1 file changed, 4 insertions(+), 11 deletions(-) diff --git a/platform/repositories/gitlab.mdx b/platform/repositories/gitlab.mdx index 7c25ede..04f9c9f 100644 --- a/platform/repositories/gitlab.mdx +++ b/platform/repositories/gitlab.mdx @@ -88,17 +88,10 @@ project-level setup. The service account itself can keep Developer access. **Why these token scopes?** - - `api` lets Hacktron post review comments. With Maintainer access, it also - lets Hacktron create and manage project webhooks and read-only clone - credentials. These write operations need more than read-only API access. - - `read_api` covers reading project and merge request information, - including the diffs Hacktron reviews. - - `read_user` covers reading the connected account's profile so Hacktron - can identify the service account during connection. - - GitLab's [`api` scope](https://docs.gitlab.com/security/tokens/access_token_scopes/) - includes these read capabilities. Hacktron's connection form lists all - three scopes. Token scopes do not raise the account's GitLab project role. + - `api`: Post review comments and, with Maintainer access, manage webhooks + and clone credentials. + - `read_api`: Read project and merge request information, including diffs. + - `read_user`: Identify the connected service account.