Link the installation to your SIXTA account (a free key takes about 30 seconds). Linking names the account your reviews run under, and that's the whole setup for repositories whose migrations are plain .sql files.
Arrived here without an installation reference? Open the App's page, hit Configure, and follow the setup link again, or link from the portal.
Any pull request that changes a .sql migration gets the full report as a comment, and the SIXTA review check by sixta-connect[bot] on the head commit. Require the check in branch protection and the gate is binding. Flyway, Prisma, golang-migrate, dbmate: nothing else to configure. An optional .sixta.yml supplies engine and engine_version; undo files feed the rollback audit.
Those migrations are rendered to SQL inside your CI, so they use the workflow instead: add your free key as a repository secret named SIXTA_API_KEY and save your framework's snippet from the CI setup page. With the App installed, workflow runs post the same SIXTA review check; the App never double-reviews a repository that runs the workflow.
For linked repositories only: the pull request's changed .sql files, an optional .sixta.yml, and workflow filenames (to defer to your own CI setup). Analyzed in memory, never stored, never executed; the details are in the data-handling statement.
How the CI review works · support@sixta.ai