Deploying a tag that matches a specific pattern would be especially useful for managing deployments intended only for specific environments or ensuring that tags must match a specific standard, such as semantic versioning, before being deployed.

For example, a tag matching regex , such as may go to a staging environment whereas a tag matching such as may go to production.

I find it terrible to depend on branches to manage my deployment. It forces me to reset my Git history and/or revert changes all which is horrible to maintain in the long term.

Tags are a much cleaner way to handle that, they are meant for it, who would know.

But the main drawback of having to control it via branches is that everytime we want to make a deploy or rollback a version, we must use a development ready machine, we can't control the version from our Git cloud provider neither from the App Platform panel itself, that's a shot in the foot.

It would be great if we can specify a prefix, for example 'production-', and any tag with that prefix would trigger a deployment