I’d like to share a suggestion about the deployment experience.
Currently, if I want to switch the deployment branch of a service, I need to go into the service settings, find the Source configuration, select another branch from the dropdown, save it, and then redeploy.
This flow is understandable, but in practice it feels a bit long when I need to test different branches, temporarily switch to another branch, or redeploy a specific version. Since the current Source is already displayed on the Service Status page, it would be very convenient if it could also work as a quick action entry.
One related thing I liked in Dokploy is that the deployment page makes the auto-deploy status quite clear. Even though I personally find Zeabur more comfortable to use overall, this small detail is useful: for a production service, I can clearly control whether every code push should trigger a deployment or not.
So I think it would be helpful if Zeabur could consider showing or adding these controls closer to the Service Status / Deployment area:
- Current deployment branch
- Auto-deploy enabled / disabled status
- Quick branch switching
- An option to redeploy immediately after switching branches
Another related feature I’m wondering about is deployment webhooks.
Right now, after pushing code, I often need to open the Zeabur dashboard manually to check whether the build and deployment succeeded, and only then continue with verification. It would be helpful if a project or service could send webhook notifications when a deployment finishes.
For example, a webhook could be triggered when:
- A deployment succeeds
- A deployment fails
- A build fails
- A deployment is canceled or removed
This would make it easier to connect Zeabur with external tools such as Slack, Discord, Feishu, Telegram, or a custom monitoring system. It would also reduce the need to manually check the dashboard after every code push.
The main idea is that Source, auto-deploy, redeploy, and deployment result notifications are closely related in real usage. If these could be managed closer to the Service Status page or deployment details, it would make the deployment workflow much smoother.