Auto-Deploy on Push
Redeploy automatically when you push to GitHub — how it works without a public webhook endpoint.
DeployOS can redeploy an app automatically whenever your branch (or a tag) moves — without you needing to click Deploy by hand every time.
Why polling, not webhooks
A desktop app running on your laptop doesn't have a stable public URL for GitHub to send a webhook to. Instead, an auto-deploy toggle on the app's Overview tab starts a background watcher that periodically runs the equivalent of git ls-remote against your repo and compares it to the commit that's currently deployed. The moment it sees the branch has moved, it triggers a redeploy — same pipeline as clicking Deploy manually.
This means DeployOS needs to be open and running to catch new pushes — it isn't a server-side webhook listener. If the app is closed when you push, the next time you open it, the watcher sweeps immediately and catches up.
Deploying on tags instead of branch pushes
Enable Track tags on the auto-deploy card to redeploy when a new git tag is pushed instead of watching a branch. Useful if you cut releases deliberately (v1.2.0) rather than deploying every commit to main.
Turning it off
Flip the same toggle off on the Overview tab. Manual Deploy still works exactly as before.
💡 Tip — real inbound GitHub webhooks (and PR preview environments) need a server DeployOS controls to receive them, which is why this is poll-based for now. It's on the roadmap for a future hosted tier layered on top of your existing license.