Delivering to GitLab

Integrate your pipelines with GitLab repositories.

If you would like to fully integrate Supernova with your organization's GitLab account, you can grant Supernova access to any GitLab repository to create pull requests on your behalf. This is done by installing and authorizing the Supernova GitLab App.

If you prefer not to authorize access to a repository that contains production code, it is also possible to create a separate repository for Supernova-created data (to be used as a git submodule). This method eliminates any possibility for Supernova to access parts of the code not maintained by Supernova.

With the secure GitLab authentication, Supernova will have the following permissions:

  • Read access to metadata
  • Read and write access to code and pull requests

Authorize GitLab

To authorize GitLab from the Account → Workspace settings page:

  1. Select the Integrations tab.
  2. Under GitLab, click Connect to sign in to your GitLab account.
  3. You can then authorize via OAuth or a personal access token.

To authorize GitLab from the New pipeline dialog:

  1. Choose Open GitLab pull request as the delivery method.
  2. Click Connect GitLab to sign in to your GitLab account. You can then authorize via OAuth or a personal access token.

After your GitLab authorization is complete, you will now see a list of repositories and branches to choose from during hook or build configuration.

Revoke GitLab authorization

To revoke your GitLab authorization at any time:

  1. Go to your Workspace settings, located in the top right corner.
  2. Select the Integrations tab.
  3. Under the GitLab section, click Remove connection.

Choosing a repository and relative path

The repository you selected is where the code from a pipeline will be exported. You can also specify a relative path to export to for each pipeline separately.

The path entered is relative to the repository root, for example, lib/design-system/assets.