Goal
Use prebuilt PawSQL connectors for Tencent CODING, GitHub, and GitLab to review SQL on commits and code reviews.Prerequisites
Prepare a PawSQL workspace, review policy, and a least-privilege identity before configuring a connector.Available connectors
Tencent CODING
Connect a CODING project and repository.
GitHub
Review SQL on pushes and pull requests.
GitLab
Review SQL on pushes and merge requests.
Connector responsibilities
- Maintain the connection between the source platform and PawSQL.
- Map organizations, repositories, branches, workspaces, and policies.
- Listen for supported repository events.
- Select SQL changes that match path and file rules.
- Create and correlate PawSQL review jobs.
- Return gate status and a secure report link.
Repository connector versus pipeline connector
Repository connectors center on push, pull-request, and merge-request events. The BlueKing connector runs as a pipeline step. To control review from Jenkins, GitHub Actions, or another pipeline without a prebuilt connector, use the OpenAPI pipeline pattern.Common setup sequence
1
Prepare PawSQL context
Create the workspace and review policy and issue a least-privilege identity.
2
Create the repository connection
Choose the platform and complete authentication or authorization.
3
Select repositories and events
Limit repositories, target branches, and push or code-review events.
4
Define the SQL scope
Configure paths, extensions, and exclusions.
5
Configure the gate
Choose blocking thresholds, failure behavior, and feedback.
6
Run acceptance tests
Exercise pass, block, no-change, and duplicate-event cases.