Hello @clphillips and everyone else in this thread!
I'm very sorry for the delay, but I wanted to let you know that I've compiled all of this great feedback into a feature request and have sent it off to the product team. I can't say if or when this feature might be implemented, but when it is implemented, it will be announced in the GitHub Changelog.
We also need to be able to delete protected branches without being a developer for "feature/*" branches for instance that once merged into master cannot be deleted easily.
We have to ask to an admin (me) and this doesn't scale way or we have to change the branch policy, delete the branch, then re-set the branch policy again... this is annoying right ?
Any update on this?
I don't see why delete protection must be a default for all branch protections. Can you not just have it as an extra tick box and let us decide whether we need this functionality?
Eg. we might want to use branch protections only to enforce status checks for feature branches that need to be deleted after a PR. Currently, not even GitHub can delete those branches following a merged PR even if the Automatically delete head branches option is selected.
For those who join this thread late or who have been waiting, I checked my branch protection rules today and found the feature implemented!
You can find the new force push and branch deletion rules at the bottom of the branch protection rule page for the branch name pattern you would like to apply rule to: