Korekt

Credential Hierarchy: This repository inherits credentials from your organization. You can override specific credential types with repository-specific credentials if needed. Manage organization credentials →

Pull Request Tracking

Track PR created/merged events via webhooks (GitHub, Bitbucket, Azure DevOps)

Using organization-level PR tracking credentials

GitHub

GITHUB_TOKEN

Select a PR tracking provider:

GitHub Credentials

Track PR created/merged events across all repos in your organization. Webhook is auto-configured.

Organization *

Your GitHub organization name (from github.com/{org}). All repos in this org will be tracked.

Personal Access Token *

Create a fine-grained token at github.com/settings/tokens?type=beta
Resource owner: your organization
Repo permissions: Contents (Read), Pull requests (Read & write), Commit statuses (Read & write), Issues (Read & write)
Org permissions: Webhooks (Read & write)
Note: Issues permission is needed for GitHub Issues ticketing integration

Bitbucket Credentials

Track PR created/merged events across all repos in your workspace. Webhook is auto-configured.

Atlassian Email *

Your Atlassian account email (used for Bitbucket login)

Workspace Slug *

From your URL: bitbucket.org/{workspace}/... — All repos in this workspace will be tracked.

API Token *

Create at id.atlassian.com/manage-profile/security/api-tokens
Required scopes:
Delete: delete:webhook:bitbucket
Read: read:webhook:bitbucket, read:repository:bitbucket, read:pullrequest:bitbucket
Write: write:webhook:bitbucket

Azure DevOps Credentials

Track PR created/merged events across all repos in your project. Webhook is auto-configured.

Organization URL *

From your URL: dev.azure.com/{organization}

Project *

From your URL: dev.azure.com/{organization}/{project} — All repos in this project will be tracked.

Personal Access Token *

Create at dev.azure.com/{organization}/_usersSettings/tokens — Required scope: Code (Read & Write)

Ticketing System

Configure access to your issue tracking system

Using organization-level ticketing credentials

JIRA

JIRA_URL JIRA_USERNAME JIRA_API_TOKEN

Select a ticketing system:

JIRA Credentials

JIRA credentials for ticket information and updates (scoped API tokens)

Email *

JIRA account email

Site Name *

From your URL: {site-name}.atlassian.net

Cloud ID *

Visit {site-name}.atlassian.net/_edge/tenant_info to get your cloudId

API Token *

Create at id.atlassian.com/manage-profile/security/api-tokens — Required: read:jira-work, write:jira-work

Azure DevOps Boards Credentials

Azure DevOps work items integration

Organization URL *

Project *

Personal Access Token *

Token with Work Items (Read & Write) permissions

GitHub Issues Credentials

Use GitHub Issues for ticket context and review summaries — uses your existing GitHub connection (App or PAT)

AI Provider

Configure access to AI services (Google Gemini)

Using organization-level AI provider credentials

No organization AI provider credentials configured.

Select an AI provider:

Google Gemini Credentials

API key for Google Gemini AI model

API Provider *

AI Studio: aistudio.google.com | Vertex AI: console.cloud.google.com/vertex-ai

Gemini API Key *

Get your API key from the selected provider