GitLab Integration

GitLab.com (SaaS)

Creating a Personal Access Token

1. Log in to gitlab.com

2. Go to User Settings → Access Tokens

3. Create a new token with the following details:

   • Name: Tidra (or any descriptive name)
   • Expiration date: Set an expiration (we recommend 90 days or less)
   • Scopes: Select the following:
     • api (Access the authenticated user's API)
     • read_repository (Read repositories)
     • write_repository (Write to repositories)

4. Click Create personal access token

5. Copy the token immediately (you won't be able to see it again)

Adding GitLab.com to Tidra

1. Navigate to Integrations in the left sidebar
2. Select the GitLab tile
3. Select GitLab.com from the dropdown
4. Paste your Personal Access Token in the Access Token field
5. Click Install Integration

---

GitLab Self-Managed

Prerequisites

• A self-managed GitLab instance (version 13.0 or later recommended)
• Network access from Tidra to your GitLab instance
• Admin or maintainer access to the repositories you want Tidra to work on

Creating a Personal Access Token

1. Log in to your GitLab instance

2. Go to User Settings → Access Tokens

3. Create a new token with the following details:

   • Name: Tidra (or any descriptive name)
   • Expiration date: Set an expiration (we recommend 90 days or less)
   • Scopes: Select the following:
     • api (Access the authenticated user's API)
     • read_repository (Read repositories)
     • write_repository (Write to repositories)

4. Click Create personal access token

5. Copy the token immediately (you won't be able to see it again)

Adding Self-Managed GitLab to Tidra

1. Navigate to Integrations in the left sidebar
2. Select the GitLab tile
3. Select Self-Managed from the dropdown
4. Enter your GitLab instance URL in the URL field (e.g., https://gitlab.yourcompany.com)
5. Paste your Personal Access Token in the Access Token field
6. Click Install Integration

Network Requirements

Your self-managed GitLab instance must be accessible from Tidra. This means:

If your GitLab is behind a firewall:

• Allowlist Tidra's IP addresses (contact support for the current list)
• Ensure HTTPS (port 443) is accessible

If your GitLab uses a private/self-signed certificate:

• Contact support - we may need to configure trust for your certificate

---

What Tidra Can Do

Once connected, Tidra will be able to:

• Read your repositories
• Create branches for code changes
• Open merge requests for review
• Update existing merge requests

---

Security Best Practices

Use a dedicated service account:

• Create a separate GitLab account for Tidra (e.g., tidra-bot)
• Grant this account access to your repositories
• Use a PAT from this account instead of your personal account
• This allows you to:
  • Easily audit what Tidra is doing
  • Revoke access without affecting your personal account
  • Set appropriate permissions for automation

Token management:

• Set token expiration dates
• Rotate tokens regularly
• Store tokens securely
• Revoke tokens you're no longer using

Repository access:

• Only grant the service account access to repositories where Tidra should work
• Use GitLab's permission system to control access levels

---

Troubleshooting

GitLab.com

"Authentication failed" error:

• Verify your token has the required scopes (api, read_repository, write_repository)
• Check that the token hasn't expired
• Ensure the token is from an account that has access to your repositories

Can't see certain repositories:

• Verify the account that created the token has at least Reporter access to those repositories
• Check that the repositories aren't archived

Merge requests aren't being created:

• Verify the account has Developer or Maintainer access to the repository
• Check that the repository allows merge requests

Self-Managed

"Cannot connect to GitLab" error:

• Verify your GitLab URL is correct (include https://)
• Check that Tidra can reach your GitLab instance (network/firewall)
• Verify the URL doesn't include /api/v4 - Tidra adds this automatically

"Authentication failed" error:

• Verify your token has the required scopes
• Check that the token hasn't expired
• Ensure the token is from an account that has access to your repositories

"SSL certificate verification failed" error:

• Your GitLab instance may be using a self-signed certificate
• Contact Tidra support to configure certificate trust

Can't see certain repositories:

• Verify the account that created the token has at least Reporter access
• Check that the repositories aren't archived

Merge requests aren't being created:

• Verify the account has Developer or Maintainer access
• Check that the repository allows merge requests

---

GitLab Version Compatibility

Self-Managed: Tidra supports GitLab version 13.0 and later. We recommend GitLab 15.0 or later for the best experience.