The GitLab integration allows you to manage your environments directly from your GitLab repository.

Features supported:

  • Create a new environment when creating a branch or opening a pull request on GitLab.
  • Rebuild the environment when pushing new code to GitLab.
  • Delete the environment when merging a pull request.

Before you begin 

To manage source integrations, you need to be a project admin.

1. Generate a token 

To integrate your project with an existing GitLab repository, generate a project access token (you can use a personal access token but a project access token has more limited permissions). Note that for the integration to work, your GitLab user needs push access to the repository.

  1. In GitLab, navigate to the project you want to integrate.
  2. In the Settings menu, choose Access Tokens.
  3. Give the token a name such as “ Integration”.
  4. (Optional) set an expiration date.
  5. Ensure the token has the following scopes:
    • api (to access your API)
    • read_repository (to read the repository)
  6. Create the token.
  7. Copy the token and save it somewhere (you can’t see it again.).

2. Enable the integration 

To enable the integration, use either the CLI or the Console.

Run the following command:

platform integration:add --type=gitlab --token=GITLAB_ACCESS_TOKEN --base-url=GITLAB_URL--server-project=NAMESPACE/PROJECTNAME --project=PLATFORM_SH_PROJECT_ID
  • GITLAB_ACCESS_TOKEN is the token you generated in step 1.
  • GITLAB_URL is the base URL to call the GitLab API. It’s if your repository is hosted on GitLab. Otherwise, it’s the base URL for your GitLab instance.
  • NAMESPACE/PROJECTNAME is the namespace of your GitLab repository, not including the base URL.
  • PLATFORM_SH_PROJECT_ID is the ID for your project.

For example, if your repository is located at, the command is similar to the following:

platform integration:add --type=gitlab --token=abc123 --base-url= --server-project=sandbox/application --project=abcdefgh1234567

Optional parameters:

  • --build-merge-requests: Track and deploy merge-requests (true by default)
  • --build-wip-merge-requests: If set to true, draft merge requests also have an environment created. If false, they’re ignored. If --build-merge-requests is false, this value is ignored. (true by default)
  • --merge-requests-clone-parent-data: Should merge requests clone the data from the parent environment (true by default)
  • --fetch-branches: Track and deploy branches (true by default)
  • --prune-branches: Delete branches that don’t exist in the remote GitLab repository (true by default)
  • --base-url: Only set if using self-hosted GitLab on your own server. If so, set this to the base URL of your private server (the part before the user and repository name).

Note that the --prune-branches option depends on --fetch-branches being enabled. If --fetch-branches is disabled, --prune-branches is automatically be set to false, even if specifically set to true.

  1. Select the project where you want to enable the integration.
  2. Click Settings.
  3. Under Project settings, click Integrations.
  4. Click + Add integration.
  5. On the GitLab integration, click + Add.
  6. Add the token you generated.
  7. Optional: If your GitLab instance is not hosted at, enter its base URL.
  8. Choose the repository to use for the project.
  9. Check that the other options match what you want.
  10. Click Add integration.

3. Validate the integration 

Verify that your integration is functioning properly using the CLI:

platform integration:validate

Add the webhook 

If the integration was added with correct permissions, the necessary webhook is added automatically. If you see the message Failed to read or write webhooks, you need to add a webhook manually:

  1. Get the webhook URL by running platform integration:get
  2. Copy the hook_url.
  3. Go to your GitLab repository and click Settings > Webhooks.
  4. Paste the hook URL. In the Trigger section select Push events, Tag push events, and Merge request events. Click Add webhook.

You can now start pushing code, creating new branches or opening merge requests directly on your GitLab repository. You see environments get automatically created and updated on the side.

Environment parent and status 

Environments based on GitLab merge requests have their target branch set as their parent on They’re added as active environments with a copy of the parent’s data.

Environments based on branches always have the default branch set as their parent on They’re added as inactive environments with no data or services.

Clones and commits 

You can clone your codebase by running platform get <projectID> or in your project in the console by going to Code > Git and running the git clone command.

When you perform this action, you are actually cloning from your remote integrated repository, if you have the appropriate access to do so.

Your GitLab repository is considered to be the source of truth for the project. The project is only a mirror of that repository and all commits should be pushed only to GitLab.

Environment URL 

For merge requests, the integration reports the primary URL for the deployed environment. So you get a link to the deployed environment right in the merge request.

If you have multiple routes, ensure the correct one is reported by specifying the primary route.