Radial app

Publishing

Publishing is git: commit, push, and your host deploys. Radial keeps your edits isolated on a staging branch so main is never dirtied directly, and ⌘⇧Return ships when you're ready.

The branch model

Edits you make in Radial live on the radial/staging branch. That gives you a working buffer between "I changed something" and "it's live." Nothing lands on your production branch until you publish there.

Staging

Publish to staging pushes the radial/staging branch. On a repo connected to Vercel, that produces a preview deploy: a real URL you (or a client) can check before anything touches production.

Production

Publish to production follows the project's policy: either push straight to main, or open a pull request for review.

Per-project configuration

Publish policy lives in a committed .radial.json at the repo root, so it travels with the repo and every collaborator (or client) inherits the same behavior:

{
  "productionPublish": "direct" | "pr",
  "productionBranch": "main",
  "stagingBranch": "radial/staging"
}

Set "productionPublish": "pr" for client repos where production changes should be reviewed, and "direct" where you own the site and want one-click ship.