Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow selecting protected branches by pattern #14461

Closed
jsil3601 opened this issue Jan 25, 2021 · 4 comments
Closed

Allow selecting protected branches by pattern #14461

jsil3601 opened this issue Jan 25, 2021 · 4 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@jsil3601
Copy link

This is a suggestion for improvement.
My knowledge of gitea code or go Lang is insufficient to pr this.

Currently, to add a branch to 'branch protection' , we need to create the branch, goto repo settings, and then select it individually from drop down, and set its security setting (allowed push teams, voters etc).
This means every time we have a new release branch, we need to go through this process, which is repetitive and prone to human error.

It will be very helpful if we could add a pattern, (such as release*, similar to how we select branches by pattern in the 'webhooks' page) thus allowing to select the protection settings by pattern and not one by one. As new branches are added in the future if they match the pattern they will also be protected.

Is this feature interesting to the gitea community /devs?

Thanks

@lunny
Copy link
Member

lunny commented Jan 26, 2021

Hm, I think there is already an issue to report this.

@jsil3601
Copy link
Author

I didn't find such an issue... Is this something that's planned for implementation?

@lunny
Copy link
Member

lunny commented Jan 26, 2021

I think this is a duplicate of #2529 . There is no plan for that.

@jsil3601
Copy link
Author

Yes you are right it's a duplicate. Can this be looked at for a future release?

@lunny lunny closed this as completed Jan 30, 2021
@lunny lunny added the issue/duplicate The issue has already been reported. label Jan 30, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Mar 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

2 participants