Connecting GitLab

What you need

1. A base URL — gitlab.com, or your self-managed instance's own URL (no default is guessed, so a self-managed customer's token never gets sent to the wrong host)
2. The project — either group/project (e.g. acme/api) or its numeric ID
3. A personal or project access token with the api scope

"Draft" is a title prefix, not a field

GitLab has no draft boolean the way GitHub does — a merge request is a draft when its title starts with Draft:, which is exactly what gets set automatically. GitLab refuses to merge a merge request whose title carries that prefix.

Self-managed and username/password

gitlab.com no longer accepts username/password for API access — an access token is the only option there. Some self-managed instances, typically ones fronted by an LDAP/Kerberos reverse proxy, still accept HTTP Basic auth; that mode is offered only for GitLab, and only as a fallback.

Set it up

1. Connectors → Add connector → GitLab
2. Enter the base URL, project, and base branch, and paste the token (or switch to username & password for a self-managed instance that needs it)
3. Click Test connection — it shows the project's full path and default branch