SQL review in your engineering workflow

Upcoming · Not yet deployed

Catch SQL issues
while the pull request is open.

An upcoming GitHub integration that checks changed SQL against workspace policies and puts findings on the pull request, ready for your team to review.

Discuss GitHub SQL Review See the preview

Preview the planned GitHub App and SQL policy checks.

Upcoming release: GitHub SQL Review is not yet deployed. Repository setup will be required.

A closer look at GitHub SQL Review.

Planned interface · Illustrative data

Kole by SyneHQ / GitHubUpcoming release · Static example

acme / warehouse/Pull request #42

Retire legacy customer status

SQL review

migrations/042_customer_status.sql · a81f3c2

Proposed SQL

UPDATE customers
SET status = 'archived';

SyneHQ SQL review

Changes needed

This UPDATE has no WHERE clause.

Blocking finding · File-level check

Review the intended scope and add a filter before requesting another review.

1 SQL file reviewed1 blocking findingNo database execution

Illustrative PostgreSQL finding. Static checks inform review; a passing check is not deployment approval.

Why GitHub SQL Review

Policy findings where developers review code.

Choose the repositories.

The planned GitHub App uses selected repositories and review settings for each one.

Scoped repository access

Review the changed SQL.

Bring static policy findings into GitHub checks and optional pull request summaries.

Feedback on the reviewed commit

Keep deployment deliberate.

Use the findings to revise the proposal. Database execution stays in your change workflow.

SQL review, with a separate deployment step

Put the finding beside the code

The planned Kole GitHub App reads SQL changes in selected repositories and publishes checks on the reviewed commit. Set the SQL dialect and migration directory, then enable review per repository.

Blocking findings fail the check; warnings remain visible. An optional summary brings the results into the pull request conversation.

Keep review and deployment separate

The integration does not write migration files or execute SQL. Configure GitHub branch protection separately if your team wants to require the check before merging. Continue database execution through your reviewed change process.

Explore the upcoming Schema Changes workspace for the ticket and approval side of that workflow.

Before you get started

A few useful answers.

Talk through your use case

Can I install this integration today?

GitHub SQL Review is upcoming and not yet deployed. The planned setup uses a GitHub App installation, selected repositories, and repository-specific review settings.

Will it deploy or change my migrations?

No. It reads changed SQL and publishes static policy findings on the reviewed commit. It does not write migration files, validate the live schema, or execute database changes.

Does a failed check automatically prevent merging?

A repository administrator must configure GitHub branch protection or a ruleset to require the check. A passing check is not approval for database execution.

Bring SQL findings into the code review.

Discuss the repositories, dialects, and review policies your team needs.

Discuss GitHub SQL Review

Catch SQL issueswhile the pull request is open.