Closed
Description
With the last version, you could only protect branches that exists. But I think it should also be possible to protect branches given as wildcard (similar to GitLab),
e.g.
pu/*
release/*
*-stable
{user}/* (this branch should be protected except {user}
I think it would be a good idea to set these attitudes globally for an organization.
Activity
stale commentedon Feb 12, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
mbarinc commentedon Sep 16, 2019
there are news about this feature?
lafriks commentedon Sep 18, 2019
I'm thinking to work on this for 1.11 version
mbarinc commentedon Sep 23, 2019
thank you @lafriks
davidsvantesson commentedon Oct 21, 2019
I think that should be a separate issue / pr to not make this too big. It need to consider some thing, like should it be a default branch setting that can be changed or deactivated in each repository?
With wildcard support it is possible that several settings match one branch, so the priority / combination of different branch protections need to be considered. Should only the first matching branch be used (means it must be possible to order them) or the most restrictive or the most permissive setting be used? What if there are different users/teams configured in different matching branch protection settings?
30 remaining items