Skip to main content

Source Control Integrations

Source control integrations enable code repository management, version control, and collaboration.

The following source control integrations are available:

GitHub

Experimental integration

This integration is currently in Experimental release status. The connection may be subject to significant changes and optimizations. We recommend using the integration in controlled testing environments.

Use the Biggy GitHub integration to add code context or investigate recent code changes, pull requests, commits, and diffs.

Required Permissions

In GitHub, ensure the following personal access token (PAT) repository permissions are enabled:

  • Metadata 

  • Commit statuses 

  • Contents 

  • Issues 

  • Pull requests 

  • Checks 

Configure the GitHub Integration

To configure the integration, populate the following fields:

Field

Description

Authentication Method

Choose how you'd like to authenticate with this integration. The following methods are available:

  • Token (PAT) - Authenticate using a GitHub token (classic PAT or fine-grained PAT)

  • OAuth Access Token - Authenticate using a secure OAuth access token

  • GitHub App (Installation token) - Server-to-server auth via GitHub App JWT + installation access tokens

GitHub API Base URL

Enter the base URL of your GitHub instance. (for example, https://api.github.com)

Credentials

If you selected Token (PAT) as your authentication method, enter your Access Token.

If you selected OAuth Access Token as your authentication method, enter your OAuth Access Token.

If you selected GitHub App (Installation token) as your authentication method, enter your GitHub App ID, GitHub App Installation ID, and GitHub App Private Key (PEM).

Custom Headers (Optional)

Add custom HTTP headers to include with all API requests. For each header, include the Header Name and Header Value. To add additional headers, click the + sign.

Deployment Type

Select whether your GitHub integration is Cloud or On-Prem.

Certain integrations have endpoints that work only with one deployment type. Selecting the correct option automatically applies the right guardrails to the Biggy agents.

Note: On-prem integrations can connect via the Relay Client, enabling secure communication with infrastructure behind your firewall.

GitHub System/Schema Nuances

List any special repo nuances, naming conventions, or other knowledge that helps Biggy more effectively interact with your tool.

We highly recommend configuring this field, as it lets you enter organization-specific information that helps Biggy provide more accurate and consistent results.

For example, you can enter key repos to prioritize, repo naming conventions, default branches, CI nuances, monorepo layout notes, deployment information, and any investigation playbooks that Biggy should follow.

GitLab

Beta integration

This integration is currently in beta release status.

Beta integrations are still being tested, but can be enabled by any customer. Core connectivity is stable, but the integration may receive updates based on user feedback.

Use the GitLab integration to investigate recent code changes, merge requests, commits, diffs, and CI/CD pipelines.

Required permissions

Ensure the following GitLab scopes/permissions have been enabled for Biggy to have the required system access to perform its functions:

Access Token Scopes

read_api read_repository

OAuth Application Scopes

read_api read_repository

Multi-integration configuration

You can configure multiple instances of GitLab.

To add an additional integration, click + Add Instance on the integration configuration page.

To configure the integration, populate the following fields:

Field

Description

Authentication Method

Choose how you'd like to authenticate with this integration. The following methods are available:

  • PAT / GAT: Authenticate using a GitLab Personal, Project, or Group access token.

  • OAuth Token (Static): Authenticate using a single OAuth access token. Note: GitLab OAuth access tokens expire after 2 hours; use OAuth (refresh) for long-lived sessions.

  • OAuth (refresh-capable): Authenticate via a GitLab OAuth application using clientId + clientSecret + refreshToken. Access tokens auto-refresh. Rotated refresh tokens are persisted automatically.

GitHub Base URL

Enter the GitLab Base URL (For example, GitLab.com: https://gitlab.com; Self-Managed: https://gitlab.yourcompany.com)

Credentials

If you selected PAT / GAT as your authentication method, enter your Access Token.

If you selected OAuth Token (Static) as your authentication method, enter your OAuth Access Token.

If you selected OAuth (refresh-capable) as your authentication method, enter your OAuth Application ID, OAuth Application Secret, and Initial Refresh Token.

Custom Headers (Optional)

Add custom HTTP headers to include with all API requests. For each header, include the Header Name and Header Value. To add additional headers, click the + sign.

Configuration Options

Select whether your GitLab integration is Cloud or On-Prem.

Certain integrations have endpoints that work only with one deployment type. Selecting the correct option automatically applies the right guardrails to the Biggy agents.

Note: On-prem integrations can connect via the Relay Client, enabling secure communication with infrastructure behind your firewall.

Routing Instructions

Routing Instructions are only required if you are configuring multiple instances of GitLab.

Enter instructions for when this specific GitLab instance should be used.

GitLab System/Schema Nuances

List any special repo nuances, naming conventions, or other knowledge that helps Biggy more effectively interact with your tool.

We highly recommend configuring this field, as it lets you enter organization-specific information that helps Biggy provide more accurate and consistent results.

For example, you can enter key repos to prioritize, repo naming conventions, default branches, CI nuances, monorepo layout notes, deployment information, and any investigation playbooks that Biggy should follow.

In this section: