Skip to main content
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

1

Create the PawSQL integration

Select the organization, project, default workspace, and policy. Retain the generated webhook URL and secret.
2

Add the webhook in CODING

Open the target repository settings and add the URL and secret supplied by PawSQL.
3

Select events

Enable the push and merge-request actions required by your workflow. Avoid unrelated events.
4

Configure mapping and filters

Restrict repositories, target branches, SQL paths, and file types, then verify the workspace mapping.
5

Test delivery

Send a CODING test event or update a test branch and confirm that PawSQL creates the expected job.
6

Validate the gate

Exercise both a passing change and a predictable blocking violation.

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.
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.

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.