Thank you for this feature request. The reason it is set this way is because many people choose to deploy from the default branch. Cancelling builds mid-deploy can be bad, hence this setting.
We are considering UI options to make this more flexible. Some ideas would be:
- enable whitelisting or blacklisting of branches related to this setting
- allow auto-canceling of all branches as an option - with a warning about deployment implications
- auto-detect if the branch has a deploy action associated with it and then don’t auto-cancel on that branch
Any suggestions or feedback on how best to implement this gratefully received