delimit_deploy_site
Deploy a static or Next.js site to Vercel by committing and pushing local changes through a governed pipeline with automatic environment injection.
Instructions
Ship a static / Next.js site via git push to the Vercel pipeline (Pro).
When to use: to deploy UI / site changes (typically delimit-ui or a venture marketing site) — this performs the commit, push, and triggers the Vercel build that produces the production deployment. Pair with delimit_deploy_verify on the resulting deploy URL to confirm rollout health. When NOT to use: to publish an npm package (use delimit_deploy_npm), to push container images (delimit_deploy_publish / delimit_deploy_build), or to roll back (delimit_deploy_rollback).
Sibling contrast: delimit_deploy_publish ships container
images; delimit_deploy_npm publishes packages; this is the
static-site / Vercel flavour. Compared to running git push
by hand, this wraps the push with sanitisation, governance
hooks, and (for delimit-ui) automatic ChatOps env-var
injection from CHATOPS_AUTH_TOKEN.
Side effects: gated by require_premium — unlicensed callers
receive a license payload and no deploy runs. project_path is
sanitised via _sanitize_path; paths escaping the workspace root
short-circuit with an error. On a licensed call, invokes
backends.tools_infra.deploy_site which performs LOCAL git
operations (add, commit, push) and triggers a NETWORK deploy
(Vercel build webhook). For the delimit-ui project, automatically
injects ChatOps env vars from the CHATOPS_AUTH_TOKEN environment
variable into the build context. No rollback — use
delimit_deploy_rollback if the deploy regresses.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| project_path | No | Path to the site project. Default "." (cwd). Sanitized — must not escape the workspace root. | . |
| message | No | Git commit message for the deploy commit. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||