Skip to main content
Sevalla connects to GitLab.com through an OAuth application named MyKinsta (Sevalla is a Kinsta product). Once you authorize it, Sevalla lists every project you’re a member of, deploys from the one you pick, and adds a webhook to the project so pushes and merge requests reach Sevalla.

​
How the GitLab connection works

​
Connect GitLab

1

Start from a repository picker

In the sidebar, click Applications, then click Create and Application. Under Source, keep Private repository, pick GitLab, then click Connect to GitLab. The same button shows when you create a static site or set up preview apps.
2

Authorize the application on GitLab

In the new tab, sign in to GitLab.com if needed, then click Authorize MyKinsta.
3

Go back to Sevalla

Return to the Sevalla tab. It picks up the connection on its own; if it doesn’t, click Check again.
The Source section of the create application page with GitLab picked as Git provider and a Connect to GitLab buttonThe Source section of the create application page with GitLab picked as Git provider and a Connect to GitLab button
GitLab's page MyKinsta is requesting access to your account on GitLab.com, with Access the API on your behalf and an Authorize MyKinsta button
Repository now lists your GitLab projects. If you create a project while the page is open, click the refresh button next to Repository.

​
Automatic deployments and the webhook

When you turn on automatic deployments for a service, or preview apps for a pipeline, Sevalla adds a webhook to the GitLab project, or updates the one it added earlier. You can see it in the project’s Settings > Webhooks on GitLab. Don’t delete it: without it, pushes and merge requests don’t reach Sevalla.
GitLab lets only Maintainers and Owners of a project add webhooks. At least one Sevalla user with the Maintainer or Owner role on the project must have connected GitLab, or the webhook isn’t added and pushes don’t deploy.
If pushes don’t deploy, check that the webhook exists. To add it again, a Maintainer connects GitLab to Sevalla, then you turn automatic deployments off and on again on the service: see Deploy automatically on push for applications and static sites.

​
Merge request preview apps

Pipelines with preview apps treat merge requests as pull requests: The preview app’s status and link are posted as a comment on the merge request. GitLab doesn’t get deployment statuses from Sevalla.

​
Disconnect GitLab

1

Revoke in Sevalla

In the user menu, click My account. In Git login & repository access, click Revoke on GitLab’s Repository access line, then Revoke in the dialog.
2

Revoke on GitLab

If GitLab’s Login is disabled too, Sevalla opens GitLab’s Applications page in your user settings (https://gitlab.com/-/user_settings/applications). Under Authorized applications, revoke MyKinsta.
Projects that no other connected Sevalla user can access are disconnected, and Sevalla removes their webhooks if your account could manage them. Services that deploy from those projects stop deploying. See Revoke repository access.

​
If a project is missing

For deployments that fail because a project isn’t available anymore, see Troubleshoot builds and deployments.

​
API and CLI