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

> ## Agent Instructions
> PawSQL 是一个产品：Cloud 是公网部署形态，Engine / Optimizer / Auditor / Advisor / Patroller 是同一产品的组件与交付形态，不是彼此独立的产品。 / PawSQL is a single product: Cloud is the public deployment form, while Engine / Optimizer / Auditor / Advisor / Patroller are components and delivery forms of the same product, not separate products.
> 术语以站内术语表为准：SQL 审核对应英文 SQL Review，查询重写对应 Query Rewrite，索引推荐对应 Index Recommendation；英文内容统一用 Review，不用 Audit。 / Use the site glossary for terminology: 审核 is SQL Review, 重写 is Query Rewrite, 索引推荐 is Index Recommendation; English content uses Review, never Audit.
> 引用能力范围或版本支持时以对应页面为准；标注 unknown、或 status 非 published 的内容表示尚未经产品核实，不应作为事实引用。 / Cite capability scope and version support from the corresponding page; content marked unknown, or with a status other than published, is not yet product-verified and must not be cited as fact.

# Integrate Tencent CODING

> Use the prebuilt PawSQL repository connector to review SQL on Tencent CODING commits and merge requests.

The prebuilt PawSQL CODING connector turns repository events into SQL review jobs and returns the resulting decision to code review and release governance.

## Goal

Use the prebuilt PawSQL repository connector to review SQL on Tencent CODING commits and merge requests.

## Before you begin

* Confirm that your PawSQL release includes the CODING webhook integration.
* Prepare a PawSQL project, workspace, and review policy.
* Obtain permission to manage webhooks in the CODING project.
* Verify that CODING can reach the PawSQL webhook endpoint.
* Select a non-production repository and branch for acceptance testing.

## Configuration

<Steps>
  <Step title="Create the PawSQL integration">
    Select the organization, project, default workspace, and policy. Retain the generated webhook URL and secret.
  </Step>

  <Step title="Add the webhook in CODING">
    Open the target repository settings and add the URL and secret supplied by PawSQL.
  </Step>

  <Step title="Select events">
    Enable the push and merge-request actions required by your workflow. Avoid unrelated events.
  </Step>

  <Step title="Configure mapping and filters">
    Restrict repositories, target branches, SQL paths, and file types, then verify the workspace mapping.
  </Step>

  <Step title="Test delivery">
    Send a CODING test event or update a test branch and confirm that PawSQL creates the expected job.
  </Step>

  <Step title="Validate the gate">
    Exercise both a passing change and a predictable blocking violation.
  </Step>
</Steps>

## Acceptance criteria

* CODING reports successful event delivery.
* The PawSQL job references the correct repository, revision, and branch.
* The expected SQL, locations, workspace, and policy are used.
* Authorized users can open the report.
* A blocking finding prevents the protected workflow from proceeding.
* Duplicate delivery does not create conflicting statuses or comments.

<Note>
  Menu labels and feedback options can differ by PawSQL release. If the CODING integration is not visible, ask the PawSQL administrator to confirm the installed version and license scope.
</Note>

## Verification

Confirm CODING reports successful event delivery and that a blocking finding prevents the protected workflow from proceeding.

## FAQ

If CODING reports successful delivery but PawSQL does not create a review, check the event action, repository allowlist, signature secret, and workspace mapping. For details, see [Troubleshoot CI/CD Integrations](/en/user-guide/cicd/logs-troubleshooting).