Auto-Cancel running deployments on git push

[JensUweB]

In our company, we have the following problem:
One of our enterprise customers has 20 deployments all based on the same GitLab repository.
Webhooks are enabled. If I push changes into the main branch, all 20 deployments (4 in parallel in our case) start running.
As you may guess, this will take a while. Now if someone pushes another commit into main we have 40 pending deployments clogging up the build server.

DigitalOcean has solved this on their platform pretty well: If a git push is received, the pending / running deployment is canceled and a new one based on the new commit is created.
Can we get that for Coolify as well?

[rujorgensen]

+1 — this hits self-hosted setups too, not just enterprise-scale ones.

My case: a monorepo on a self-hosted Gitea deploying several apps to one Coolify server via webhooks. Every merge to main queues a deployment for every app, and since the queue is FIFO per server, merging a few times in a row means every app first builds all the stale commits before the newest one gets its turn. I recently found 27 queued deployments, almost all of them for commits that were already superseded.

The DigitalOcean behavior described above would solve this cleanly: when a new deployment is queued for an application, cancel any still-queued (not yet started) deployments for the same application, since they can only ever produce an outdated result. Even without touching running builds, just superseding queued ones would eliminate most of the wasted work.

Happy to help test if this gets picked up.