Native locking with custom scopes?


Any plans to implement CircleCI-native locking, to ensure that two tasks of a particular kind don’t run at the same time? Serializing Deployments helps a little, but is somewhat limited in only being able to lock on the branch, tag, or global level. Being able to create specific locks and acquire them would be more flexible.