[PrePush::ProtectedBranches] Implement setting destructive_only per branch

[ChrisBr]

PrePush::ProtectedBranches supports a destructive_only setting. However, this setting is globally valid for all protected branches. It makes sense to set this setting on a per branch basis. This PR implements the following syntax for the configuration of ProtectedBranches.

PrePush:
  ProtectedBranches:
    enabled: true
    branches:
      - protected
      - protected_for_destructive_only:
         destructive_only: true

In case it is not set on a branch it will fall back to the global setting. Additionally it will use the setting of the first matching branch.

Example:

PrePush:
  ProtectedBranches:
    enabled: true
    branch_patterns:
      - releases/*
      - releases/v1:
         destructive_only: true

In this case, a push to releases/v1 would be forbidden because releases/* would match which uses the global setting for destructive_only. The solution in this case would be to flip the order of the branch definitions.

Credit for this idea goes to @davidstosik 🎉

[sds]

Thanks @ChrisBr. Can you also update the docs for ProtectedBranches to mention this functionality?

Otherwise, looks reasonable to me. Once you transition this from a draft happy to merge. Thanks!

[ChrisBr]

@sds updated the documentation 👍

Thanks

[ChrisBr]

That was quick, thank you very much @sds 🎉

[ChrisBr]

Is there a plan to release a new version anytime soon?

[sds]

0.52.0 has been released.