Skip to content
SQLAnvil SQLAnvil SQLAnvil

Code (read-only workspace)

The Code page is a read-only workspace: pick a branch, browse the repo tree, and view any file with syntax highlighting. It is deliberately not an editor — authoring happens locally with your agent and git — but everything you’d want for review is here:

  • Branch-scoped tree — files come straight from GitHub via the SQLAnvil app installation; nothing is cloned or stored.

  • Compiled SQL toggle — for a .sqlx model, flip between the source and the SQL it compiled to. The compiled view comes from the branch’s latest release (pinned compilation snapshot) and is labeled with the commit it was compiled at — cut a release on the Workflows page if the branch doesn’t have one yet.

  • Model metadata — target, action type, tags, dependencies, and dependents, from the same compiled graph.

  • Results preview — for a model with a compiled release, the Results tab queries the warehouse directly (first 100 rows), two ways:

    • Current data reads the materialized object — what the last completed run produced. Run the workflow (Run now), wait for it to finish, and preview again to see the fresh data.
    • Compiled query executes the release’s stored SELECT without materializing anything — what the model would produce, even before it has ever run. For an assertion, rows returned are failures.

    Previews are read-only by construction: the SQL comes from the stored release (never from the browser), runs through the same revocable Supabase authorization as workflow runs, and is wrapped so anything but a single SELECT is rejected. Nothing is stored — rows go straight to your screen.

  • Graph view — the branch’s latest release drawn as a dependency DAG, data flowing left to right: tables, views, incrementals, assertions, sources and operations color-coded, each node clickable through to its file. Because it renders from the stored release, the graph always matches a specific commit (labeled), not a guess about the working tree.

  • Open in VS Code — one click opens the file in github.dev, the full VS Code web IDE against your own repo and GitHub login, for when you want real editor ergonomics.

Together with run history and per-action detail, this completes the review loop: read the model, read what it compiled to, read how it ran — all without granting anything write access.