Documentation
Release flow
Deployments
Deployments move source code into a site release while preserving logs, selected run details, webhook state, and release history.
Updated Jun 22, 2026
2 min read
What deployments do
Deployments move source code into a site release while preserving status, logs, selected run details, webhook state, and release history. A deployment should be treated as an operational record, not just a command that ran once.
Before deploying
- Confirm the source provider is connected and synced.
- Review the repository, branch, tag, deploy key, and webhook settings.
- Check the deployment script for dependency installs, cache commands, migrations, and release activation.
- Make sure backup and rollback expectations are clear for production sites.
Typical workflow
- Connect GitHub or GitLab.
- Attach the repository and branch to the site.
- Review the deployment script and environment values.
- Run a manual deployment or enable push-to-deploy.
- Inspect the deployment result, duration, output, and selected run details.
Checks before enabling push-to-deploy
- The manual deployment path works first.
- The deploy key can read the repository.
- Webhooks are attached to the expected branch.
- The deployment script is safe for production.
- Notifications are routed to the right team destination.
Common issues
- A deploy fails because the deploy key is missing or stale.
- A migration runs without a backup plan.
- Push-to-deploy is enabled on the wrong branch.
- Failed deployments are retried without reading the output.