mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
mintlify[bot]
15 lines
1.6 KiB
Plaintext
15 lines
1.6 KiB
Plaintext
## GitLab setup
|
|
|
|
To use GitLab repositories in a workflow, connect each project through the [GitLab OAuth](https://app.mintlify.com/settings/organization/gitlab-oauth) settings page. Connect every repository the workflow touches—your documentation repository and any trigger or context repositories.
|
|
|
|
The authorizing user needs both of the following on each project's **top-level group**:
|
|
|
|
- **Developer role or higher on the top-level group.** The repo picker only lists projects inside top-level groups where the connecting user has Developer or higher. Project-level access alone is not enough—if you are added as Maintainer on a single project but do not have Developer+ on its top-level group, the project will not appear in the picker and cannot be authorized. Personal projects (projects in a user's personal namespace) are surfaced under a separate **Personal projects** entry and do not require group-level access.
|
|
- **Maintainer role or higher on the project itself.** Once the project is visible, Mintlify needs Maintainer on the project to mint the short-lived project access tokens the agent uses to push commits and open merge requests.
|
|
|
|
If your organization only lets you hold Maintainer on the project (not Developer on the group), ask a group owner to either grant you Developer+ on the top-level group for the initial authorization, or have someone who already has Developer+ on the group authorize the connection.
|
|
|
|
<Note>
|
|
Workflows require a paid GitLab tier. The agent uses short-lived project access tokens for repository access, which GitLab's Free plan does not support.
|
|
</Note>
|