Pull request lifecycle
Preview records identify the pull request, source branch, current status, URL, and latest deployment.
Preview environments
Give every pull request somewhere real to run.
Create an isolated scale-to-zero application environment for an open pull request, with a dedicated managed URL and explicit teardown when the review is finished.
Review the running change, not a screenshot
Preview compute is ephemeral. Copying or branching data remains an explicit choice so opening a pull request does not silently replicate production state.
Dedicated managed URL
Each preview serves from its own generated hostname without taking over the production environment.
Scale-to-zero runtime
Preview application compute can idle without paying for an always-on runtime.
Inherited access policy
A project can declare how preview access inherits from its application policy rather than relying on obscurity.
Replaceable releases
The preview tracks its latest deployment so reviewers see which revision is currently running.
Explicit teardown
Remove the preview and release its application route when the pull request no longer needs an environment.
Workflow
Open, review, remove
- 01
Open a pull request
The preview is associated with one review and receives its own application environment and hostname.
Scope isolated - 02
Deploy the change
Build state and logs remain inspectable while the latest successful release serves reviewers.
Revision visible - 03
Close the lifecycle
Teardown removes the preview application environment; retained project history stays in the control plane.
Resources released