Deployable Naming Convention
I believe a natural extension to the existing branch-specific deployment is to add pattern matching. Given a pattern, such as deploy/* or [deploy]*, all branches meeting that criteria will pass. In doing so, developers can easily deploy staging/*, release/*, support/*, d-feature/* without interruption to workflow or cluttering deployments with all branches.
Accordingly, patterned context names would come before branch-specific names so they can be overridden if necessary. Also, similar to branch-specific deploys, a subdomain equivalent to the star would aid accessibility.
[context.'deploy/*'] command = "build command"
My Use Case
In my particular use case, hundreds of collaborator branches may be generated at any given time. Though only a subset of these may require deployment. Being able to add a tag or naming convention enables me to isolate only functional changes.