GitLab self-managed configuration #153
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughDocumentation updates in self-hosting/govern/integrations: GitHub guide receives indentation-only formatting fixes; GitLab guide is restructured into tabbed Cloud vs Self-managed flows with updated steps, screenshots, links, and scoped permissions, plus configuration and activation details tailored per edition. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
self-hosting/govern/integrations/github.mdx (1)
75-134: Restore ordered-list indentation inside the GitHub Enterprise tab.Dropping the two leading spaces before list items 2‑7 breaks the numbered list inside the tab—MDX treats them as separate paragraphs, so the order resets in the rendered docs. Please re-indent those items (match the Cloud tab) to preserve the sequence.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
self-hosting/govern/integrations/github.mdx(3 hunks)self-hosting/govern/integrations/gitlab.mdx(2 hunks)
|
|
||
|  | ||
|
|
||
| 8. Set permissions by selecting the required **Scopes**. The table below explains each scope: | ||
|
|
||
| |Permission|Explanation| | ||
| |----------|-----------| | ||
| |`api`|Grants full read/write access to the API, including all groups, projects, container registry, dependency proxy, and package registry. Required for API requests.| | ||
| |`read_api`|Allows read-only access to all groups, projects, container registry, and package registry.| | ||
| |`read_user`|Grants read-only access to user profiles via the /user API endpoint, including username, public email, and full name. Also provides access to /users endpoints.| | ||
| |`read_repository`|Enables read-only access to repositories in private projects via Git-over-HTTP or the Repository Files API.| | ||
| |`write_repository`|Allows read/write access to repositories on private projects via Git-over-HTTP (not through the API).| | ||
| |`profile`|Grants read-only access to the user's profile data using OpenID Connect.| | ||
| |`email`|Provides read-only access to the user's primary email address using OpenID Connect.| | ||
|
|
||
| 9. Click **Save Application** to finalize the setup. | ||
| </Tab> |
There was a problem hiding this comment.
Mark the app as confidential—secret is required later.
Step 7 says the Confidential checkbox is optional, but the Configure Plane section instructs users to copy the application “Secret.” GitLab only issues a secret when the application is confidential, so leaving it unchecked breaks the integration flow. Please update the instructions to require Confidential.
🤖 Prompt for AI Agents
In self-hosting/govern/integrations/gitlab.mdx around lines 47 to 63, the guide
currently treats the "Confidential" checkbox as optional while later instructing
users to copy the application's Secret; since GitLab only issues a secret for
confidential applications, change the step to require selecting "Confidential"
(mark it as required/checked) and update any related wording to instruct users
to check the Confidential box so the application Secret will be generated for
use in Configure Plane.
Description
Type of Change
Screenshots and Media (if applicable)
Test Scenarios
References
Summary by CodeRabbit