GitHub integration | Prisma Compute

Connect a GitHub repository to a project and Prisma deploys on every push, with previews tracking your Git branches.

Connect a GitHub repository to a project and Prisma deploys on every push. Branch and push events map to platform branches automatically, so your previews track your Git branches.

How it works

The connection has two levels:

How a GitHub connection deploys on pushStep 1 of 3

The connection has two levels. First, your workspace installs the Prisma GitHub App once. That installation is what lets Prisma see your repositories.

The workspace owns the GitHub App installation; each project points at a single repository. Once connected, Prisma listens for that repo's branch events and keeps the matching platform branches in sync.

In beta, a project connects to one repository.

Connect a repo

From a linked project directory, connect your Git origin:

bunx @prisma/cli@latest git connect

To name the repository explicitly:

bunx @prisma/cli@latest git connect https://github.com/acme/shop

If the GitHub App isn't installed yet, the CLI starts the install flow. In --json / --no-interactive mode it doesn't block: it gives you the install URL to finish in the browser, so automation can hand the install off:

bunx @prisma/cli@latest git connect https://github.com/acme/shop --json --no-interactive

Disconnect when you're done:

bunx @prisma/cli@latest git disconnect

Disconnecting stops future automation. It doesn't delete the project or tear down existing branches.

What events do

Once a project is connected:

Branch created → creates the matching platform branch.
Push → creates or resolves the matching branch and builds the pushed commit.
Branch deleted → tears down the matching branch, unless it's the production or default branch.

Connecting doesn't deploy anything on its own; it wires up automation for future events. To deploy right now, run app deploy yourself.

CI and monorepos

Auto-deploy handles monorepos that declare their apps in prisma.compute.ts: one pushed commit fans out into a targeted build per app. For custom pipelines, or anywhere you want full control, run the CLI directly with a service token and explicit targets:

PRISMA_SERVICE_TOKEN=... npx @prisma/cli@latest app deploy \
  --project my-app \
  --app web \
  --branch "$GITHUB_HEAD_REF" \
  --json \
  --no-interactive

This keeps deploys deterministic and gives agents a structured result to read.

What's not in beta

GitHub is the only supported provider; others return REPO_PROVIDER_UNSUPPORTED. The webhook path is branch- and push-driven. Each webhook deployment posts a "Prisma Compute Deploy" check run on the commit — success or failure, with the deploy URL — on a best-effort basis. Pull-request comments and preview comments aren't part of the beta surface.

Next steps

Branching: how platform branches map to Git.
Deployments: what happens after a push builds.
Environment variables: per-branch config for previews.

GitHub