Source Control Providers#
Connect your Git provider to start receiving pull request webhooks and enable AI PR Review and Impact Analyzer. Codluma supports four providers across all plans — with GitLab requiring Pro or higher.
Provider
How to Connect
Available On
GitHub
GitHub App — automatic webhook setup, no token needed
All plans
Azure DevOps
Personal Access Token — Azure Repos and Pipelines
All plans
Bitbucket
Atlassian API Token — repositories and webhooks
All plans
GitLab
Personal Access Token — projects and MR webhooks
Pro+
GitLab source control requires a Pro plan or higher. GitHub, Azure DevOps, and Bitbucket are available on all plans including Free.
GitHub
Codluma uses a GitHub App for GitHub integration. Apps are scoped to specific organisations and repositories, can be revoked independently of any user account, and produce audit log entries for every action they perform. No personal access token is needed.
1
Navigate to Settings → Integrations → GitHub
2
Click Install GitHub AppGitHub will prompt you to select which organisations and repositories to grant access to.
3
Review permissions and click Install
4
Toggle on repositoriesGo to Repositories and enable the repos you want monitored.
Azure DevOps
Azure DevOps uses a Personal Access Token (PAT) with scopes for Code (Read) and Pull Request Threads (Read & Write). The token is encrypted at rest and never logged.
1
Create a PAT in Azure DevOpsGo to Azure DevOps → User Settings → Personal access tokens. Create a token with scopes: Code: Read and Pull Request Threads: Read & write.
2
Navigate to Settings → Integrations → Azure DevOps
3
Enter your organisation URL and PATFormat: https://dev.azure.com/your-org
4
Select projects and enable repositories
PATs expire — Codluma will notify you 7 days before expiry so you can rotate the token without any review coverage gap.
Bitbucket
Bitbucket uses an Atlassian API Token tied to your Atlassian account. The token needs read access to repositories and write access to pull request comments.
1
Create an API token at id.atlassian.comGo to Security → API tokens → Create API token. Label it something like Codluma.
2
Navigate to Settings → Integrations → Bitbucket
3
Enter your Atlassian email and API token
4
Select workspaces and enable repositories
GitLab (Pro+)
GitLab integration requires a Personal Access Token with api scope. This enables webhook registration, MR comment posting, and pipeline log access.
1
Create a PAT in GitLabGo to GitLab → Preferences → Access Tokens. Select scope: api.
2
Navigate to Settings → Integrations → GitLab
3
Enter your GitLab instance URL and PATSupports both gitlab.com and self-hosted GitLab instances.
4
Select groups and projects to enable
CI/CD Providers#
CI/CD provider integrations enable the DevOps Failure Explainer. Each connection allows Codluma to ingest raw failure logs, identify root causes, and post plain-language explanations back to the pull request that triggered the failure.
CI/CD integrations require a Pro plan or higher. Free plan organisations can connect GitHub Actions only.
Provider
Capabilities
Available On
GitHub Actions
Logs · Comments · Webhooks · Projects
All plans
GitLab CI/CD
Logs · Comments · Webhooks · Projects
Pro+
Azure Pipelines
Logs · Comments · Webhooks · Projects · Token refresh
Pro+
AWS CodeBuild
Logs · Projects
Pro+
Jenkins
Logs · Projects
Pro+
CircleCI
Logs · Projects · Token refresh
Pro+
Bitbucket Pipelines
Logs · Comments · Webhooks · Projects · Token refresh
Pro+
GitHub Actions
GitHub Actions is the only CI/CD provider available on the Free plan. Codluma receives failure events via the same GitHub App used for source control — no additional configuration is needed once your GitHub App is installed.
GitLab CI/CD
Requires your GitLab PAT to have the read_api scope in addition to api. Webhooks are registered automatically when you enable a project. Failure logs are fetched directly from the GitLab Jobs API.
Azure Pipelines
Uses the same Azure DevOps PAT as source control. Additional PAT scope required: Build: Read. Codluma supports automatic PAT refresh to avoid expiry-related gaps in coverage.
Jenkins, AWS CodeBuild & CircleCI
These providers use webhook-based log delivery. Install the Codluma plugin (Jenkins) or configure a webhook endpoint in your pipeline settings. Full setup guides are available under Settings → Integrations in the dashboard once you select the provider.
Notification Channels#
Codluma can push review and failure analysis notifications through four channels. Slack, Microsoft Teams, and custom webhooks require a Pro plan or higher.
Channel
What Gets Sent
Available On
Email
PR review complete, new findings, failure analysis ready
All plans
Slack
Review summaries, failure explanations, merge readiness
Pro+
Microsoft Teams
Review summaries, failure explanations, merge readiness
Pro+
Custom webhook
Full JSON payload for every review and analysis event
Pro+
Slack Setup
1
Go to Settings → Notifications → Slack
2
Click Connect SlackYou'll be redirected to Slack's OAuth flow. Authorise Codluma to post to your workspace.
3
Select a default channelPick the channel where review notifications should appear. You can override this per repository.
4
Choose notification typesToggle on PR review complete, failure analysis, and/or merge readiness notifications independently.
Microsoft Teams Setup
1
Go to Settings → Notifications → Microsoft Teams
2
Click Connect TeamsAuthorise the Codluma app via Microsoft's OAuth flow.
3
Select a team and channel
4
Choose notification types
You can configure separate Slack or Teams channels per repository. Go to Repositories → [repo name] → Notification overrides.