Conversation
GitLab Group access tokens are Premium/Ultimate only and add confusion without clear benefit over a dedicated Personal access token service account. Remove the tab entirely and flatten the remaining Personal access token flow at the section root. - Delete the Group access token tab - Unwrap the single Personal access token tab so steps render as a top-level numbered list - Outdent the fine-grained alternative and its permission tables by one indentation level (also addresses Copilot reviewer concern about deeply-indented tables) - Update intro, prerequisites, create-token lead, and Project-token warning to reference only Personal access tokens - Shorten frontmatter description accordingly (134 chars) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
🤖 kluster.ai PR Review Summary⚡ Review this PR in 1/10 of the time — Try our new AI-powered code review experience 📋 PR SummaryThis PR updates the GitLab PR Reviews Setup documentation to simplify the instructions for connecting the kluster.ai bot to GitLab. The changes remove references to Group access tokens and focus solely on using a Personal access token for the integration. The documentation still provides detailed steps for creating a Legacy personal access token or a fine-grained personal access token, but emphasizes the recommended use of Legacy tokens. The changes aim to clarify and streamline the setup process. ✅ All ClearNo issues detected in this PR.
Powered by kluster.ai - Real-Time AI code review in your IDE |
There was a problem hiding this comment.
Pull request overview
Removes the GitLab Group access token setup option from the GitLab PR Reviews integration docs to reduce confusion and streamline the setup flow around Personal access tokens.
Changes:
- Updates frontmatter + intro/prerequisites to reference only Personal access tokens.
- Removes the Group access token tab and flattens the Personal access token instructions into a single top-level flow.
- Outdents the fine‑grained token alternative (including its permission tables) to reduce deep nesting.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Start the Legacy-token lead-in with "The kluster.ai bot uses..."
instead of "kluster uses...". This:
- Keeps the kluster brand rule (lowercase k, even at sentence start)
- Avoids a lowercase sentence start
- Matches the adjacent sentence on the line above the warning ("The
kluster.ai bot requires a GitLab personal access token...")
- Is more semantically precise: the PR bot component uses the token,
not the whole kluster.ai service
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
🤖 kluster.ai PR Review Summary⚡ Review this PR in 1/10 of the time — Try our new AI-powered code review experience 📋 PR SummaryThis PR updates the documentation for setting up GitLab PR reviews with kluster.ai. The changes remove references to "Group access token" and emphasize using a personal access token for the integration. The documentation now consistently recommends using a Legacy personal access token, but still provides an alternative section on creating a fine-grained personal access token for users who need to restrict repository access. Overall, the PR simplifies the token options and clarifies the recommended setup process. ✅ All ClearNo issues detected in this PR.
Powered by kluster.ai - Real-Time AI code review in your IDE |
|
@0xlukem can you please review this one (even though it's already been merged) and make follow up edits if needed? |
Description
GitLab Group access tokens are Premium/Ultimate only and add confusion without clear benefit over a dedicated Personal access token service account. Remove the tab entirely and flatten the remaining Personal access token flow at the section root.
Checklist
kluster-mkdocsrepo