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.

Sign up for GitHub

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

Jump to bottom

Branch protection with regex support #4024

Closed
2 of 8 tasks
sebastian-sauer opened this issue May 23, 2018 · 1 comment
Closed
2 of 8 tasks

Branch protection with regex support #4024

sebastian-sauer opened this issue May 23, 2018 · 1 comment
Labels
issue/duplicate The issue has already been reported.

Comments

@sebastian-sauer
Copy link
Contributor

sebastian-sauer commented May 23, 2018 •
edited
Loading

  • Gitea version (or commit ref): 1.4.1
  • Git version: not relevant
  • Operating system: not relevant
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
    • not relevant
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Currently branch protection is only available for named branches. In order to e.g. only allow specific colleagues to push into release branches it would be great if we could configure a regex for branch protection. This would allow us to protect all branches matching release and not having to protect each individual branch.

Screenshots
@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label May 23, 2018
@lafriks
Copy link
Member

lafriks commented May 23, 2018

There is already feature request for this #2529

@lafriks lafriks added issue/duplicate The issue has already been reported. and removed type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 23, 2018
@lafriks lafriks closed this as completed May 23, 2018
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lunny @lafriks @sebastian-sauer