docs: clarify GitLab OAuth top-level group requirement#6384
Closed
mintlify[bot] wants to merge 1 commit into
Closed
docs: clarify GitLab OAuth top-level group requirement#6384mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Callout from a customer (
bango) support thread: GitLab users could not connect a docs repo for automations even after being granted Maintainer on the project itself, because the repo picker only surfaces top-level groups where the connecting user has Developer or higher. Project-level Maintainer is separately required to mint tokens once the project is visible.Updates:
snippets/gitlab-automation-setup.mdxandsnippets/gitlab-workflow-setup.mdx— split the access requirement into two bullets (Developer+ on top-level group to appear in the picker, Maintainer+ on the project to mint tokens) and add a workaround for orgs that can only grant project-level access.deploy/gitlab-self-hosted.mdx— same split in the "Choose projects" step of the self-hosted flow, plus a clarification that only top-level groups with Developer+ are listed.Localized snippets (
es,fr,zh) are left for the translation workflow to re-sync from the English source.Generated by Mintlify Agent.
Requested by: patrick@mintlify.com via Slack
Mintlify session: slack_1783093815.533469_C09TP13PJTH
Note
Low Risk
Documentation-only updates to GitLab OAuth setup guidance; no application or security behavior changes.
Overview
Documents why GitLab repos can stay missing from the OAuth picker even when a user has Maintainer on the project alone.
GitLab automation and workflow setup snippets now spell out two separate requirements: Developer+ on the top-level group so projects show in the picker (project-only Maintainer is insufficient), and Maintainer+ on the project so Mintlify can mint tokens for pushes and merge requests. They also add guidance when org policy blocks group-level access.
Self-hosted GitLab “Choose projects” step matches that model—listing only top-level groups where the user has Developer+, and expanding the note with the same two-tier access explanation and workaround.
Reviewed by Cursor Bugbot for commit 51ea24d. Bugbot is set up for automated code reviews on this repo. Configure here.