Auto-deploy on push

With auto-deploy enabled, Velumi listens for GitHub push events on your tracked branch and triggers a deployment automatically — no manual button, no GitHub Actions, no extra GitHub-side setup beyond the initial GitHub App install.

Enabling auto-deploy

Open the environment, go to the Source tab, and toggle Auto-deploy on push on.

• The toggle shows which branch is being watched (e.g. "Deploys automatically when you push to main.")
• If the environment inherits the project source and no branch is set, it watches the repository's default branch.
• Requires Owner or Admin role in the organization.

How it works

When you push to the tracked branch:

1. GitHub sends a push event to Velumi via the GitHub App webhook.
2. Velumi matches the push to environments that have auto-deploy enabled and track that repo and branch.
3. A deployment is queued — identical to triggering one manually from the dashboard.
4. If a deployment is already running when the push arrives, the new push is queued and deploys automatically once the current one finishes.

No extra permissions or GitHub App configuration are needed. The App is already authorized to receive push events on all installations.

Limitations

• GitHub sources only. Auto-deploy is not available for archive (upload) sources — there is no push event to listen to.
• Branch must match. Only pushes to the exact branch the environment tracks trigger a deploy. Pushes to other branches are silently ignored.
• Tag pushes and branch deletes do not trigger deploys.

Disabling auto-deploy

Toggle Auto-deploy on push off on the environment's Source tab. Subsequent pushes will no longer trigger deployments for that environment.

Relationship to manual deploys

Auto-deploy and manual deploys are not mutually exclusive. You can still trigger a deployment manually at any time — auto-deploy simply adds an automatic trigger on top.