IntegrationsGitLab

GitLab Integration

Clacky’s GitLab integration enables seamless collaboration between your development workspace and GitLab repositories. This integration allows you to manage repositories, track issues, create merge requests, and manage CI/CD pipelines directly from your Clacky environment.

Connection Setup

Follow these steps to connect Clacky with your GitLab account:

1. Generate a Personal Access Token

First, you need to create a Personal Access Token (PAT) in GitLab:

  1. Log in to your GitLab account
  2. Click on your profile picture in the top-right corner
  3. Select “Preferences” from the dropdown menu
  4. Navigate to “Access Tokens” in the left sidebar
  5. Fill in the following details:
    • Token name: A descriptive name (e.g., “Clacky Integration”)
    • Expiration date: Select a date (maximum 365 days)
    • Scopes: Select the required permissions (see Required Permissions section)
  6. Click “Create personal access token”
  7. Important: Copy the generated token immediately as it will only be shown once

2. Add the Token to Clacky

  1. Click “Create Project”, select “GitLab”, and follow the authorization process
  2. In the form, enter your GitLab instance URL (default is https://gitlab.com)
  3. Paste your Personal Access Token (PAT)
  4. Click “Connect”. After connecting successfully, you’ll see a list of your repositories.
  5. Select a repository to connect, and Clacky will automatically create a project and clone the repository for you.

Configuration Options

Authentication Renewal

GitLab Personal Access Tokens may expire based on your GitLab settings. To renew:

  1. Generate a new token in GitLab following the steps in the first section
  2. Go to Clacky’s “Integrations” > “GitLab” settings
  3. Click “Update Token”
  4. Enter your new token
  5. Click “Save”

Troubleshooting

Connection Issues

If you’re experiencing connection problems:

  1. Verify your Personal Access Token hasn’t expired
  2. Check that your GitLab instance URL is correct
  3. Ensure your network allows connections to GitLab
  4. Try disconnecting and reconnecting the integration

Permission Denied

If you receive “Permission denied” errors:

  1. Check that your token has the necessary scopes (api, read_repository, etc.)
  2. Verify you have appropriate access to the repository in GitLab
  3. For private repositories, ensure your token has the right permissions

Repository Not Found

If repositories are missing from the list:

  1. Make sure you have access to the repository in GitLab
  2. Check if the repository is from a GitLab instance different from your connected one
  3. Try searching for the repository by name or URL

Frequently Asked Questions

Can I connect multiple GitLab accounts?

Currently, Clacky supports one GitLab account connection per workspace. If you need to switch accounts, disconnect the current one before connecting a new one.

Is my GitLab token secure?

Yes, your Personal Access Token is stored securely and encrypted. Clacky never shares your token with third parties.

Does the integration work with self-hosted GitLab instances?

Yes, the integration works with both gitlab.com and self-hosted GitLab instances. When connecting, simply provide the URL of your GitLab instance.

How do I disconnect my GitLab account?

To disconnect your GitLab account:

  1. Go to “Workspace - Settings” > “Integrations” > “GitLab”
  2. Click “Disconnect”
  3. Confirm the disconnection

Resources

Integrations