Connecting a repository

Last updated: June 24, 2026

AISLE integrates with your version control system to analyze repositories for security issues and open automated fix PRs. This page covers what all supported VCS providers have in common. For provider-specific setup steps, follow the linked guide for your platform. More information on repositories can be found in Repositories.

Provider

Authentication Method

Guide

GitHub

Dedicated GitHub App (installed per org)

GitHub Integration

GitLab (SaaS, Self-Managed, Dedicated)

Personal Access Token on a service account

GitLab Integration

Bitbucket Cloud

API Token on a dedicated user

Bitbucket Cloud Integration

Azure DevOps

Personal Access Token

[Azure DevOps Cloud Integration]

Prerequisites (All Providers)

Before starting any VCS integration, ensure you have the following:

  • Sufficient permissions in your VCS platform to create a service account (or install an app) and grant it access to target repositories. See the provider-specific guide for exact role requirements.

Adding a VCS Connection in AISLE

If this is your first VCS connection, you’ll be prompted during initial AISLE setup — the onboarding flow requires at least one repository.

To add a connection after initial setup, navigate to Repositories in the left panel (or go to https://<customer>.env.aisle.cloud/app/repositories) and click the + Add <Provider> button for the platform you’re connecting.

Note that AISLE supports connecting multiple instances of the same provider (e.g., several GitLab instances or GitHub organizations). Repeat the provider-specific steps for each.

General Workflow

Regardless of provider, VCS integration follows the same pattern:

  1. Create a dedicated identity in your VCS platform (a service account, bot user, or app installation) so AISLE’s actions are clearly attributable in audit logs.

  2. Grant it access to the target repositories with the minimum permissions required (detailed in each provider guide).

  3. Copy/paste the authentication credential (PAT, API token, or app key) AISLE shared with you during onboarding.

  4. Add the connection in AISLE and select which repositories to analyze.

💡  Onboarding note

Steps 3 and 4 (entering the credential into AISLE and selecting repositories) are typically completed during your onboarding call with the AISLE team.

Off-boarding

When your engagement ends, revoke the credential you created, whether it be a PAT, API token, or app installation. Each provider guide includes specific revocation steps. To preserve audit history, consider deactivating the service account rather than deleting it.