Deploy
Auto-deploy
auto-deploy connects a GitHub project to a branch. When enabled during creation, each push to the selected branch triggers a new publication automatically.
When to enable
Enable auto-deploy when:
- the configured branch is stable
- the team uses pull requests or review before merge
- every push to the branch should become a new published version
- the application has tests or validation before reaching the watched branch
Avoid enabling it on experimental branches or branches used for local work.
How it works
- the project is created with GitHub Repository source
- you choose branch, runtime, version, and commands
auto-deployis enabled during creation- a push to the selected branch triggers the build flow
- Zenifra updates the instance when publication finishes successfully
If auto-deploy is disabled, pushes do not update the project automatically.
What to validate
After a push:
- check build logs
- confirm the application responds on the public URL
- review application logs
- validate metrics and HTTP requests
- confirm the published version, if the application exposes commit or version
Common failures
| Symptom | Likely cause |
|---|---|
| Push did not trigger deploy | auto-deploy was not enabled or branch differs |
| Build failed | wrong command, missing dependency, or inconsistent lockfile |
| App crashed after deploy | wrong port, missing variable, or startup error |
| Wrong version is live | push was made to a branch different from the configured one |
Next steps
FAQ
Can I enable auto-deploy later?
In the current documented flow, auto-deploy is defined during GitHub project creation. Plan this decision before creating the project.
Does auto-deploy exist for OCI?
Not in the same format. OCI projects are updated by changing the published image.
Does the build run on every push?
When auto-deploy is enabled, pushes to the configured branch trigger a new publication.