<public-url> below for your stable public Roomote URL.
Create a GitLab bot token
Create a dedicated GitLab bot or service-account user and add it to the groups or projects Roomote should access. Create an access token for that identity with scopes that match the behavior you want:| Scope | Needed for |
|---|---|
api | project listing and repository sync through REST |
read_repository | cloning private repositories over Git-over-HTTPS |
write_repository | pushing branches or commits from Roomote tasks |
.env.local:
GITLAB_BASE_URL.
Sync repositories
After the token is available, open Settings, go to the Environments page, and use the Source Control section’s GitLab sync button. Roomote lists the GitLab projects visible to the token and stores them as GitLab repository rows. GitLab-backed tasks clone from the synced repository row, so sync must run before launching a GitLab-backed task.Configure webhooks
Create a GitLab project or group webhook for merge request events. Webhook URL:- Merge request events
Enable review automation
GitLab merge-request reviews use the same Review Code automation targeting model as GitHub. After syncing repositories, associate the GitLab repository with the intended environment and enable Review Code automation for that target. Open or reopened merge request events enqueue initial review tasks. Update events enqueue sync reviews when GitLab includesoldrev, which indicates a
code-related update.
Verify setup
- sync GitLab repositories from Settings
- create or update an environment from a synced repository
- start a small task and confirm Roomote can clone the repository
- open or update a merge request and confirm configured review automation runs