Catch SQL issues in the pull request.

A workspace administrator connects the GitHub installation, synchronizes the repositories selected in GitHub, and explicitly enables review for each repository. Set its SQL dialect and migration directory to define what the review should inspect. Repository review starts disabled; pull request summary comments are a separate option.

The installation's selected repositories define the access boundary. Workspace settings cannot expand access beyond that selection. The integration reads repository contents and publishes checks and review feedback; it does not write migration files or deploy them to your database.

A pull request that changes SQL in the configured directory receives a SyneHQ SQL review check. Findings use the workspace's enabled policies for that dialect, with built-in safeguards when no policy is enabled. Blocking findings fail the check; warnings remain visible without failing it.

An optional bot summary brings the findings into the pull request conversation. The check is attached to the reviewed commit, and the summary identifies that commit so a reviewer can tell which version was inspected. Review history and rerun controls remain available in SyneHQ.

These are static checks, not a migration dry run, schema validation, or a guarantee that SQL is safe. A passing check does not approve database execution. GitHub merge enforcement requires a repository administrator to configure branch protection or a ruleset that requires the check.

For execution, continue through the reviewed change workflow and the target database's permissions. Installing the GitHub App does not automatically deploy migrations.