Allowlist for deleting branch with branch protection #10968

New Issue

GiteaMirror · 2025-11-02T09:23:36-06:00

GiteaMirror commented

2025-11-02 09:23:36 -06:00

Originally created by @YifanAtBioRoboLab on GitHub (Jun 5, 2023).

Feature Description

Our team find branch protection a powerful tool and one way we are using it is to set rules for different branch name patterns to prevent mispush to a wrong branch.

However, we have noticed there is no easy way to delete such protected branches from any users (even those in the push whitelist).

We need a method to assign specific users to delete the protected feature branches after they are merged.

The best practice we can think of is to have another whitelist about how is allowed to delete (and rename) a specific branch the rule is protecting. But we failed to find this feature if already existing.

Additional option to only allow deleting for merged branches will also be beneficial for us.

Screenshots

No response

Originally created by @YifanAtBioRoboLab on GitHub (Jun 5, 2023). ### Feature Description Our team find branch protection a powerful tool and one way we are using it is to set rules for different branch name patterns to prevent mispush to a wrong branch. However, we have noticed there is no easy way to delete such protected branches from any users (even those in the push whitelist). We need a method to assign specific users to delete the protected feature branches after they are merged. The best practice we can think of is to have another whitelist about how is allowed to delete (and rename) a specific branch the rule is protecting. But we failed to find this feature if already existing. Additional option to only allow deleting for merged branches will also be beneficial for us. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature labels 2025-11-02 09:23:36 -06:00

GiteaMirror commented

2025-11-02 09:23:37 -06:00

@panangam commented on GitHub (Jun 16, 2023):

Seconding this. This makes a lot of sense to me. Why can't we also have whitelist for force push as well?

@panangam commented on GitHub (Jun 16, 2023): Seconding this. This makes a lot of sense to me. Why can't we also have whitelist for force push as well?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#10968