Automatic deployment

Hallvi deploys each new commit on your branch within about a minute of a push. You set up nothing on GitHub.

In short

Hallvi deploys one commit at a time, and each commit only once.
It needs a GitHub connection, even for a public repository, and a first release that Hallvi verified.
A failed commit waits until you press Retry or push a newer commit.

You pushto main

Hallvi checksGitHub, about once a minute

Started automaticallya message in the main conversation

Deploy and checkdeployed, or failed

then waits for the next commit

The rules

One at a time. When an attempt ends, the newest commit goes next. Hallvi skips the ones in between.
Once per commit. A failed commit waits for Retry or a newer commit.
Verified only. A commit counts as deployed only if the check of the running application passed.
After a break. Hallvi finds the newest commit it missed. An attempt it could not finish shows interrupted, and waits for you.

Control it

Hallvi asks during the first deployment: Automatically when main changes, or Only when I ask. Change it later on the Deployment page, or ask in the conversation.

On the Deployment page	What it does
Pause, Resume	Pause holds deployments. New commits wait on the page.
Deploy latest	Deploys the newest commit now.
Retry	Tries a failed or interrupted commit again.
Deployment settings	Switch between automatic and manual, or change the branch.

What it needs

Hallvi running and online. It pauses while a Mac sleeps.
A GitHub connection, even for a public repository.
A first release that Hallvi verified.

In Always ask, each command of an automatic deployment still waits for your approval.