prisma-platform-core-concepts

Run prisma deploy module.ts --stage <name> to create a branch named after the stage and deploy the identical app graph into it. The stage name must be a valid git ref name, and the preview gets its own fresh database wired as a branch-scoped DATABASE_URL.

Connect the repository with prisma git connect or via the Console, then every push builds and deploys automatically. Pushes to the default branch deploy production, while pushes to other branches create or update preview environments without any workflow file.

A preview environment is torn down when its upstream git branch is deleted, or reclaimed automatically if it sat idle and unpinned. Push or deploy the branch again to re-create it, but the database starts empty since data does not persist.

No, environment variable values are write-only by design. Listing shows only names and scopes, and no API returns values; to change a value you replace it, then re-deploy since variables resolve at deploy time.

The Compute runtime has no global Temporal object, so reading an ORM DateTime column throws RUNTIME.TEMPORAL_UNAVAILABLE. Add the temporal-polyfill dependency and import it at the service entry, or use the String column types such as TimestamptzString.

The CLI branch group only lists branches; there is no create or delete verb. Branches are created by pushing or deploying a stage and removed by deleting the upstream git branch, and failed builds cannot be retried except by the next push or deploy.