GitLab connects using a personal access token. Configure it at Settings → Connections → Source control.
Creating the token
In GitLab, create a personal access token with the api scope. This covers reading repository contents, creating branches, and opening merge requests.
Paste it into the source control settings. Coroid encrypts it at rest, never returns it via the interface or API, and never includes it in settings exports.
Token ownership
For shared team use, create the token on an account intended for automation rather than an individual's, so the connection remains active even when people change roles.
Set an expiry date that you will actually track. A token that expires unnoticed will cause pushes to fail suddenly, leading to a confusing symptom that is hard to diagnose from the error message alone.
Merge requests
Coroid opens merge requests in the same way it opens pull requests on GitHub — one branch per task, pushed when the work is ready, and targeted at your base branch.
Your existing approval rules and pipeline requirements apply unchanged.
GitLab Review Apps
When you use GitLab Review Apps, those environments can be attached to merge requests as review evidence. See Review evidence.
Self-managed GitLab
The connection assumes your GitLab instance is reachable from Coroid. For a self-managed instance behind a network boundary, this must be sorted out before the token can be used.