GitLab

gitlab.com with a sign-in, or your own GitLab with an access token. Releavo adds the webhooks itself.

gitlab.com

1. Connectors → GitLab → Connect.
2. Enter the group or project: acme or acme/web. A group covers all its projects, subgroups included (up to 50).
3. Sign in with GitLab and approve.

Your own GitLab

1. Connectors → GitLab → Connect.
2. Paste the group's or project's full address: https://gitlab.acme.com/acme. A token field appears.
3. Paste an access token (personal, group or project) with the api scope (on gitlab.com: create a personal access token; on your own GitLab it's the same page under your-gitlab/-/user_settings/personal_access_tokens), from someone with the Maintainer role. Then Connect.

GitLab has no narrower scope that allows adding webhooks, so it asks for api. Releavo reads code and adds its webhooks; it pushes only with coding switched on, to its own releavo/ branches, and opens draft merge requests.

Projects it can't follow

Adding a webhook needs the Maintainer role. Projects where that's refused are still readable, and the connector says which ones aren't followed. Someone with the role can connect again to finish.

See How Releavo follows your code.