Repository navigation
docs: require Maintainer to connect GitLab projects via OAuth - #8433
Merged
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
N43527
approved these changes
Nov 12, 2026
This branch was successfully deployed
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
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.
States that Mintlify now refuses to connect a GitLab project over OAuth unless the authorizing user is a Maintainer (or a self-managed instance admin who isn't a member), replacing the old "read-only without Maintainer" note.
Based on a merged change that blocks connecting GitLab projects via OAuth without the Maintainer role. Duplicate check: open and recent docs PRs for "GitLab", "OAuth", "Maintainer"; none found.
Note
Low Risk
Documentation-only updates with no application or security logic changes.
Overview
Documentation now matches Mintlify’s stricter GitLab OAuth behavior: projects are not connected unless the authorizing user is at least a Maintainer (with a note that instance admins can connect projects they’re not on).
The self-hosted GitLab guide adds this to Prerequisites and replaces the old “read-only without Maintainer” note with guidance that lower roles trigger a connection error and remediation steps. The shared GitLab automation setup snippet states the same refusal-to-connect behavior for authorized accounts.
Reviewed by Cursor Bugbot for commit 26e5c1c. Bugbot is set up for automated code reviews on this repo. Configure here.