> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jataka.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Copado Integration

> How Copado and Jataka work together through GitHub pull request checks.

# Copado Integration

You do not need a custom Copado integration to use Jataka. Copado already works on top of Git, and Jataka integrates at the GitHub pull request layer.

## Enterprise Flow

<Steps>
  <Step>
    **Developer action in Copado**\
    A developer clicks **Commit and Promote** in the Copado UI.
  </Step>

  <Step>
    **Copado opens a pull request in GitHub**\
    Copado commits the metadata changes and automatically opens a pull request to merge into the target branch.
  </Step>

  <Step>
    **Jataka intercepts the PR on GitHub**\
    As soon as the PR is created, Jataka runs:

    * API Firewall
    * Tech Debt scan
  </Step>

  <Step>
    **Jataka posts check status to GitHub**\
    If Jataka detects a critical violation (for example, `Too many SOQL queries: 101`), it posts a **Failed** status check on the pull request.
  </Step>

  <Step>
    **Copado halts deployment automatically**\
    Copado listens to GitHub pull request status checks. When the Jataka check is failed, Copado stops the promotion and marks the UI state as failed (red).
  </Step>
</Steps>

## Why This Works Without a Custom Connector

* Copado is the delivery UI and orchestration layer.
* GitHub pull requests are the system of record for promotion state.
* Jataka enforces quality and guardrails directly on the PR.
* Copado consumes GitHub check results and reacts automatically.

## Example Failure Scenario

<Callout type="warning">
  A trigger introduces SOQL inside a loop. Jataka detects the `101 SOQL` anti-pattern during PR checks, sets the pull request check to **Failed**, and Copado blocks the deployment.
</Callout>

## Recommended Setup

1. Install and configure Jataka on your GitHub repository.
2. Ensure Copado is configured to promote through GitHub pull requests.
3. Require Jataka checks before merge in GitHub branch protection rules.
4. Use Copado as the release UI while GitHub + Jataka enforce technical quality gates.

## Outcome

Teams keep Copado as their familiar release interface while using Jataka as an automated quality gate on every promotion PR.